There is so much wrong with this approach: Most importantly, you now have
to support everything you supported in 0.4. But as the zero at the
beginning of the node version tells, it's not a final product. It's okay to
break features. Companies interested in the advantages of the new version
need to accept the disadvantages. That's the way jQuery does it. And it's
working.
*(As a side-note: Of course, as soon as backwards-compat isn't the main
goal anymore, every serious security hole needs to be fixed for every
version. But as those won't show up on a daily basis, it's not a big issue.)
*
Another idea: Remove the entire module, so that it won't be found anymore.
If sys is still needed, go to your home directory and run
mkdir -p node_modules/sys;echo
"module.exports=require('util')">node_modules/sys/index.js
Someone could even add a sys module to npm, containing that single line.
Congrats, fixing this issue is now adding a single entry to your
package.json.
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
