Sooo that&#x27;s like, an npm design flaw then? If you <i>don&#x27;t</i> specify the engine field, someone using an older version of node will just get incorrect failures and think your package is broken. I&#x27;d rather specify the engine and give a clear error to all users on a version of Node.js older than 1 day than to make it work for users on Node RCs. Although it would be nice if npm made it possible to support both sets of users.