On Jun 27, 2012, at 15:33, Ian Young wrote: > I share Matt's concern. I'd be bummed if I wanted to release a new version of > a module that depended on 0.8 features, but doing so would mean most of my > users on 0.6 got a broken version installed by default with only a warning to > dissuade them. Especially if there were perfectly good older versions sitting > in npm that worked on 0.6. > > Maybe npm could issue a warning on maximum version failures, but keep the old > behavior on minimum version failures. That's getting kinda complex, though. > > I wonder if this isn't better solved by guiding the community towards > removing upper limits from engines in all but the most specific cases?
To encourage this, npm could print a warning if the engines line has an upper limit. But that might be annoying for packages that actually do have an upper limit of supported node versions. -- 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
