mirror of
https://github.com/tj/n.git
synced 2024-11-28 21:22:03 +01:00
142 lines
3.9 KiB
Markdown
142 lines
3.9 KiB
Markdown
# n
|
||
|
||
My own flavour of node binary management, no subshells, no profile setup, no convoluted api, just _simple_.
|
||
|
||
## Installation
|
||
|
||
$ npm install -g n
|
||
|
||
or
|
||
|
||
$ make install
|
||
|
||
### Installing Binaries
|
||
|
||
Install a few nodes ("v" is optional), the version given becomes the active node binary once installation is complete.
|
||
|
||
$ n 0.2.6
|
||
$ n v0.3.3
|
||
|
||
List installed binaries:
|
||
|
||
$ n
|
||
|
||
0.2.5
|
||
ο 0.2.6
|
||
0.3.3
|
||
|
||
Pass some config flags to _./configure_:
|
||
|
||
$ n 0.2.6 --debug
|
||
|
||
List installed binaries, config flags are shown:
|
||
|
||
0.2.3
|
||
ο 0.2.6 --debug
|
||
0.3.4
|
||
0.3.5
|
||
|
||
Use or install the latest official release:
|
||
|
||
$ n latest
|
||
|
||
Install a custom or patched version of node from a tarball:
|
||
|
||
$ n custom 0.6.5 https://github.com/dshaw/node/tarball/patch/v0.6.5status
|
||
|
||
### Removing Binaries
|
||
|
||
Remove some versions:
|
||
|
||
$ n rm 0.2.4 v0.3.0
|
||
|
||
Instead of using `rm` we can simply use `-`:
|
||
|
||
$ n - 0.2.4
|
||
|
||
### Binary Usage
|
||
|
||
When running multiple versions of node, we can target
|
||
them directly by asking `n` for the binary path:
|
||
|
||
$ n bin 0.3.3
|
||
/usr/local/n/versions/0.3.3/bin/node
|
||
|
||
Execute a script with 0.3.3 regardless of the active version:
|
||
|
||
$ n use 0.3.3 some.js
|
||
|
||
with flags:
|
||
|
||
$ n as 0.3.3 --debug some.js
|
||
|
||
Execute npm with 0.6.3 regardless of the active version:
|
||
|
||
$ n npm 0.6.3 install coffee-script
|
||
$ n npm 0.6.3 list
|
||
|
||
## Usage
|
||
|
||
Output from `n --help`:
|
||
|
||
Usage: n [options] [COMMAND] [config]
|
||
|
||
Commands:
|
||
|
||
n Output versions installed
|
||
n latest [config ...] Install or activate the latest node release
|
||
n <version> [config ...] Install and/or use node <version>
|
||
n custom <version> <tarball> [config ...] Install custom node <tarball> with [args ...]
|
||
n use <version> [args ...] Execute node <version> with [args ...]
|
||
n npm <version> [args ...] Execute npm <version> with [args ...]
|
||
n bin <version> Output bin path for <version>
|
||
n rm <version ...> Remove the given version(s)
|
||
n --latest Output the latest node version available
|
||
n ls Output the versions of node available
|
||
|
||
Options:
|
||
|
||
-V, --version Output current version of n
|
||
-h, --help Display help information
|
||
|
||
Aliases:
|
||
|
||
- rm
|
||
which bin
|
||
use as
|
||
custom c
|
||
|
||
## Details
|
||
|
||
`n` by default installs node to _/usr/local/n/versions_, from
|
||
which it can see what you have currently installed, and activate previously installed versions of node when `n <version>` is invoked again.
|
||
|
||
Activated nodes are then installed to the prefix _/usr/local_, which of course may be altered via the __N_PREFIX__ environment variable.
|
||
|
||
To alter where `n` operates simply export __N_PREFIX__ to whatever you prefer.
|
||
|
||
## License
|
||
|
||
(The MIT License)
|
||
|
||
Copyright (c) 2010 TJ Holowaychuk <tj@vision-media.ca>
|
||
|
||
Permission is hereby granted, free of charge, to any person obtaining
|
||
a copy of this software and associated documentation files (the
|
||
'Software'), to deal in the Software without restriction, including
|
||
without limitation the rights to use, copy, modify, merge, publish,
|
||
distribute, sublicense, and/or sell copies of the Software, and to
|
||
permit persons to whom the Software is furnished to do so, subject to
|
||
the following conditions:
|
||
|
||
The above copyright notice and this permission notice shall be
|
||
included in all copies or substantial portions of the Software.
|
||
|
||
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
|
||
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
||
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
|
||
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
|
||
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
|
||
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
|
||
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|