6094dac1c1
[Fix] `nvm debug` was printing a red herring error message in non-zsh.
9 years ago
0aa3118de3
v0.30.1
9 years ago
2541baaf7d
[Refactor] Create `nvm_get_make_jobs` to abstract out “-j” logic.
9 years ago
dc8b63cb25
[Fix] `nvm install -s`: fix syntax errors.
9 years ago
8ec056f768
v0.30.0
9 years ago
f279837d5c
[Refactor] fix some bugs in `nvm_is_natural_num`, add unit tests.
9 years ago
31457fec3f
[Refactor] `nvm install`: make `-j` and `-s` order-independent.
9 years ago
e78dc5110e
fix CPU_THREADS/CPU_THREAD_VALID/MAKE_JOBS prefix
9 years ago
6320719dd8
Support parameter -j to set jobs for make
9 years ago
a8e6fee001
Enable multiple jobs for when build from source
9 years ago
6638ac3318
[refactor] improved bootstrap time
...
Fixes #860 , closes #927 .
9 years ago
04c5e3540e
`nvm unalias`: Provide a restore command when unaliasing.
...
Fixes #916 .
9 years ago
2a174d03d8
Update nvm.sh
...
Add prompt when there is no binary for node version greater than v1.0.0
Currently, on FreeBSD, if we try `nvm install 4.2`, we will only get:
> Installing node v1.0 and greater from source is not currently supported
In fact I had no idea what's wrong because I didn't use `-s` parameter for it,
and then I found that there are two reasons:
1. There was no pre-built nodejs binary from official for FreeBSD, which means we need to build from source.
2. nvm doesn't support build for v1.0 and greater version from source yet.
So I think there should be a prompt message to tell the user about the reason why nvm will go to build from source,
no matter it will succeed or fail.
9 years ago
c742ab7e66
Fix `npm` version output for `nvm run` and `nvm exec`
9 years ago
1adcabf5e8
Replace backticks with $() command substitution
9 years ago
a43ff7c9d9
Ensure that `npm` doesn't print out excess data, regardless of the user's log level.
...
Fixes #881 .
9 years ago
114f27a075
Use `nvm_ls_remote_index_tab` for listing nodejs.org versions.
...
Enabled by https://github.com/nodejs/build/issues/218 , unblocks #870 .
9 years ago
690543d6ad
Rename nvm_ls_remote_iojs_org → nvm_ls_remote_index_tab and make it generic.
9 years ago
0b9526e3b4
Don't check `$1` unless `$#` is >= 1.
...
Fixes #873 . Partially fixes #868 .
9 years ago
016e7dfdab
[nvm run / nvm exec]: Silence "find nvmrc" output when `--silent` is provided.
...
Per https://github.com/creationix/nvm/issues/846#issuecomment-147588453
9 years ago
2a0316f80d
[shellcheck] Remove useless `echo`
9 years ago
e7e28f436e
[shellcheck] double-quote vars in more places
9 years ago
84aad508f7
Check `$#` before trying to check `$1`. Avoids failure due to `nounset` bash option.
...
Partially fixes #868 .
9 years ago
8f3ee23390
[shellcheck] Correct redirection order: we want both stdout and stderr sent to /dev/null here.
9 years ago
032fab7172
`local`s need to be declared and assigned separately, for `ksh`.
9 years ago
46833efd79
[shellcheck] Remove useless `echo`
9 years ago
9407f850f1
[shellcheck] read without -r will mangle backslashes.
...
http://pubs.opengroup.org/onlinepubs/009695399/utilities/read.html / https://github.com/koalaman/shellcheck/wiki/SC2162
9 years ago
bf284203cb
[shellcheck] Declare and assign separately to avoid masking return values
...
https://github.com/koalaman/shellcheck/wiki/SC2155
9 years ago
c957989fa9
Add `nvm --version` and `$HOME` to `nvm debug`
9 years ago
e1c84bae37
v0.29.0
9 years ago
a928a8f181
nvm exec: don't fall back to `.nvmrc` when the provided version is not installed.
9 years ago
937c29c95a
nvm run: use common code path for "ensure version installed"
...
Better than cb033adc6f
9 years ago
a0e94e16de
Make sure `nvm debug` doesn't use an overridden `sed`
9 years ago
b8e4917646
Use `xz` tarballs if available
...
Saves us ~25% bandwidth while downloading the payload. This only applies
to hosts that has the `xz` binary and attempts to use iojs 2.3.2 or newer
(this includes nodejs 4.0+ as well). Older targets are unaffected.
9 years ago
cb033adc6f
nvm run: use common code path for "ensure version installed"
9 years ago
20f4acdd25
[installing] echo the URL that the tarball is being downloaded from.
9 years ago
41153e207d
Ensure `nvm use` output shows up *after* `prefix` check passes.
9 years ago
6b3c34313c
Fix `nvm_ls` when `$NVM_DIR` has spaces in it.
...
Mostly fixes #861 .
9 years ago
8541e2e1ee
Properly quote some possible variables with spaces.
9 years ago
06a21284ed
Protect against `cat` clobbering. Fixes #858 .
9 years ago
ebdcdc4363
v0.28.0
9 years ago
b805de80cb
Add `PREFIX` and `NPM_CONFIG_PREFIX` env vars to `nvm debug`
10 years ago
44f416d58f
Create and use `nvm_sanitize_path` for `nvm debug`
10 years ago
3d1ccfec70
Sort `nvm ls` results by semver version, so the order goes: "unmerged node", "iojs", "merged node".
10 years ago
2d692d9d78
Fix support for installing node on SmartOS
...
uname on SmartOS cannot be used to guess if 32 and/or 64 bits binaries
are supported, and its output is different than other uname commands on
other operating systems.
This change uses pkg_info to determine what types of binaries pkgsrc
would install. If pkg_info fails to run or is not present, this change
falls back to using isainfo -n, which determines what the kernel
supports.
It allows users to install node binaries on Solaris derivatives. io.js
can also be installed on Solaris derivatives starting with version
v3.3.1.
10 years ago
8aebf86329
v0.27.1
10 years ago
838d72688f
v0.27.0
10 years ago
8ee6f30352
Add support for `$NPM_CONFIG_PREFIX` to `nvm_die_on_prefix`.
...
Fixes #606 .
10 years ago
1458de7293
Ensure that if `npm config get prefix` is set to something outside `nvm`, that `nvm use` refuses to work.
...
Fixes #606 .
10 years ago
a1def71062
Add `nvm_die_on_prefix`
10 years ago
Jordan Harband