On Sunday, October 21, 2012 9:16:43 PM UTC+2, ack wrote: > spawns the right version of node, passing it the original app script name > and commandline parameters. The parent node process can then just exit. > I tried to write a script that restarts itself when its code was modified (like what nodemon, supervisor, etc. do, but the script itself does it). At least on Windows this doesn't seem possible without opening a new shell window in the process. If I reuse the I/O streams, the parent process does not exit. This is not what you want when running command line apps, for instance, you want the output right there where you ran the command, without a need to rearrange windows.
Also how would you handle a script that needs to run on 0.4 and then requires a module that needs to run on 0.6? I agree that the version hell is annoying, but you can't necessarily assume that people have multiple node versions installed. To me it seems that in the rare cases where node versions collide, you should create a shell script that first sets the correct version and then runs the script. This way it continues to be one command and you don't need to remember the correct version. -- 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
