![]() | Name | Last modified | Size | Description |
---|---|---|---|---|
![]() | Parent Directory | - | ||
![]() | node_modules/ | 2 years ago | - | |
![]() | bin/ | 2 years ago | - | |
![]() | README.md | 40 years ago | 965 | d7c1522 post receive test [كارل مبارك] |
![]() | package.json | 2 years ago | 1.3K | |
![]() | installArchSpecificPackage.js | 40 years ago | 45 |
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.
npm i node@lts
npx
npx node@4 myscript.js
This 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.js
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.