If you publish your module with 0.6.x you tacitly engage yourself to
maintaining it and publishing a newer version shortly after 0.8 is
released, don't you?
The rule should be to publish with >= x.y.z unless you know that some
upcoming or already released change will break your code.
If you don't know what the future will be, you should bet on the fact that
things won't break. Does not mean that they won't ever break but you'll
take action when they do. Be optimistic!.
So I don't see anything wrong with the "engines" feature itself. The
problem is that it has been misused.
Bruno
On Wednesday, June 27, 2012 7:06:52 AM UTC+2, Isaac Schlueter wrote:
>
> 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
