prefix for node packages

[chaoflow]

For perl and python we prefix packages. This should also be done for node packages. An exception might be applications written in node that are installed for the sake of having the application instead of the node package available. See #1466

[domenkozar]

+1 from me

[domenkozar]

See 2f11bc4

[shlevy]

I guess given 2f11bc4 this is now inevitable. I'll modify npm2nix to add a marker if a package contains any binaries and use that to determine if packages should get the node- prefix then add back the recurseIntoAttrs

[chaoflow]

I'm not sure whether having binaries is enough to count as an "application". nose for example is a python test tool and setuptools ships with easy_install and a couple more binaries. Both I would like to see as python2.7-nose and python2.7-setuptools, not without a prefix. Whereas offlineimap and afew, two tools concerned with handling emails, I would like to see without prefix.

[shlevy]

Well if it turns out to be a problem we can just do them all with the node prefix, but seems like a good place to start.

[shlevy]

Fixed in 3bec816