Good practice is to limit minimal engine version, but set max version
unlimited.
That's tested for ages in multiple package managers. Please, don't
experiment
with such functionality. There is nothing genious in cutting mature
concepts.
среда, 27 июня 2012 г., 9:06:52 UTC+4 пользователь Isaac Schlueter написал:
>
> Do people actually rely on the "engines" hash being respected in npm
> installs any more? It was super essential in the early days when the
> API was changing constantly, but now, it seems like it just makes it
> unnecessarily difficult to upgrade stuff.
>
> If no one is relying on this right now, I'm going to reduce it to a
> warning. If in time, people start complaining that the warning is to
> warny, we can remove it, and just let "engines" be a thing of the
> past. (Note that `npm init` already doesn't bother with it, and for a
> while has just defaulted to {"node":"*"}.)
>
> Please let me know what you think. Thanks :)
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
