🚀 Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more
Socket
Book a DemoInstallSign in
Socket

node

Package Overview
Dependencies
Maintainers
2
Versions
765
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

node - npm Package Compare versions

Comparing version

to
0.1.18

2

installArchSpecificPackage.js

@@ -1,1 +0,1 @@

require('node-bin-setup')("0.1.17", require);
require('node-bin-setup')("0.1.18", require);
{
"name": "node",
"version": "0.1.17",
"version": "0.1.18",
"description": "node",

@@ -5,0 +5,0 @@ "main": "index.js",

@@ -1,17 +0,34 @@

node-bin
node
========
Mad science ahead
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 verion 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. It is mad science after all.
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 install --save node-bin@v4-lts`
```
npm i node@lts
```
or with npm 3:
Use with `npx`
--------------
`npm install -g node-bin@v4-lts`
```
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
```
Thanks
------
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.