🚀 Fast and simple Node.js version manager, built in Rust
GPL-3.0 License
Bot releases are visible (Hide)
Published by Schniz about 5 years ago
Published by Schniz over 5 years ago
Support for lts/*
has landed. Now you can refer to the latest Node v10 as lts/dubnium
and both use
and install
will understand that. Moreover, fnm install latest
creates an alias named latest
so you can use
it without thinking about the exact version.
uninstall
(@Schniz)Published by Schniz over 5 years ago
@dangdennis has added a fnm default
command that aliases to alias default
, so it is more convenient to set a default version! Thanks Dennis!
default
, as a shortcut for alias default
(@dangdennis)Published by Schniz over 5 years ago
uninstall
command thanks to the amazing @tatchi!base
. This takes us a little further in supporting Windows!fnm use system
realpath
(@Schniz)realpath
instead of binding to C library (@Schniz)Published by Schniz over 5 years ago
@ohana54 has added a global log level option:
eval "$(fnm env --multi --log-level=quiet)"
Published by Schniz over 5 years ago
Published by Schniz over 5 years ago
Binaries are now much smaller due to stripping of the debugging metadata (~30-40% smaller!)
Published by Schniz over 5 years ago
use-on-cd
now works with .node-version
files on Zsh, thanks to a bug that was fixed by @johnletey and reported by @MoOx. Thanks friends! This path is now fully tested
Published by Schniz over 5 years ago
There's a new --use-on-cd
option to fnm env
that will change Node versions automatically based on the current working directory .nvmrc
or .node-version
.
If you already have fnm
installed,
.zshrc
, .bashrc
or .bash_profile
:
- eval `fnm env --multi`
+ eval "`fnm env --multi --use-on-cd`"
fish.config
to the following:
- eval (fnm env --multi)
+ fnm env --multi --use-on-cd | source
Published by Schniz over 5 years ago
Published by Schniz over 5 years ago
@tatchi has replaced the Http
module to use cohttp
instead of executing curl
. That means that we're one step closer to Windows support (I hope) and to a real self-contained binary. Thanks @tatchi!
Published by Schniz over 5 years ago
Inference of complete semantic version:
In order to download the latest Node 11 version:
fnm install 11
In order to use the latest installed Node 11 version:
fnm use 11
--install-dir
and --skip-shell
) (@from-nibly)vX.X.X
) out of partial input (vX
/vX.X
). (@Schniz)install
failures (@ranyitz)Published by Schniz over 5 years ago
.node-version
file support (#42, by @Dean177)fnm use
exits with exit code 1 on errors now (#45, by @Schniz)Published by Schniz over 5 years ago
By changing the line below, you can now start using fnm
with different Node versions on each shell.
- eval `fnm env`
+ eval `fnm env --multi`
It means you can now have different versions for different projects and work in parallel in splits/tabs of your favorite terminal.
A simple way of calling a version in a name:
fnm install v8.11.3
fnm alias v8.11.3 stable
fnm use stable # like `fnm use v8.11.3`
Published by Schniz over 5 years ago
Bugfix: make sure installer script works on Linux (thanks @drazik!)