Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (node) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
node
Installs a node binary into your project, which because npm runs scripts with the local ./node_modules/.bin in the PATH ahead of the system copy means you can have a local version of node that is different than your system's, and manage node as a normal dependency.
Warning: don't install this globally with npm 2. npm@2 immediately removes node, then can't run the scripts that make this work.
Use
npm i node@ltsUse with npx
npx node@4 myscript.jsThis will run myscript.js with the latest version of node from the v4 major.
Using the shell auto-fallback of npx, you can even do it like so:
node@4 myscript.jsThanks
Major thanks to Kat Marchán for late-night problem solving, and to CJ Silverio and Maciej Małecki for egging me on way back when I had the idea to package node up this way. It does turn out if you ask "why not?!" once in a while something fun happens.