Install through NPM?

[VileTouch]

as opposed to shipping with a large, outdated node executable?

[draivin]

The main issue with shipping through npm is that it would require the user to look for the npm installation directory so he could move the dll there.

Also, the primary objective of the user interface was to provide the program in a reasonably easy way to people who do not have a lot experience messing with command line stuff, and asking them to install npm beforehand would go against that.

I could create a dist branch that includes the executable and clean up the master branch and publish it to npm, but the dll issue would still be there.

Thoughts?

[VileTouch]

I think it is good to give users a choice. if they don't know what node/npm is, it doesn't bother them to dowload the whole package. for them, that IS the software. for those who have a node installation, it is cleaner, leaner and won't leave them...us wondering if it will mess up the installed references (package locations, path entries,etc.). even if it's perfectly safe (to our installed packages) and self contained.