invalid PATH detection

[max-mapper]

at nodeschool IRL events lately the #1 issue is definitely computers where global modules arent in the PATH.

i'm not a shell expert by any means but maybe we could do some sort of PATH analysis as a post-install hook or something that said very clearly:

You just installed learnyounode, use this command to run it:
learnyounode

or if their PATH is messed up:

You just installed learnyounode, use this command to run it:
/usr/local/lib/node_modules/learnyounode

[max-mapper]

also twice i've seen this crazy bug where running learnyounode on windows results in a "JScript" error, which I think is a result of usr/bin/env not being interpreted and .js files on windows try to get evaluated with JScript and not node?

[rvagg]

The "JScript" error was only happening on Windows right??

I guess we could also run some post-install stuff to check that an executable runs right; it's odd though because npm itself uses #!/usr/bin/env node and presumably they are using npm to install.

[max-mapper]

yea JScript only exists on windows