sne
Simple Node Environment (say "snee"): a fast Node.js version manager for Windows, Linux and macOS.
- One small native binary. No runtime, no shell-script framework to load on every prompt.
- No shims.
node,npmandnpxrun directly; sne is not in the way of every call. - Switching is one filesystem operation.
sne usere-points a link;PATHnever changes. - Works with your existing projects. Reads
.nvmrc,.node-versionandengines.nodeinpackage.json. - Verified installs. Every download is checked against the SHA-256 published by nodejs.org, and an interrupted install never leaves a half-installed version.
- No admin rights on Windows. Uses directory junctions, so Developer Mode is not needed.
Website | Documentation | Changelog
Status: beta (0.1.0-beta.5). The Windows build is tested end to end. The Linux and macOS code paths are covered by the test suite in CI but have had less real-world use.
Install
Windows
Run this in PowerShell. It needs no administrator rights:
irm https://raw.githubusercontent.com/sne-sh/sne/main/install.ps1 | iex
It downloads the latest release, checks its SHA-256, puts sne.exe in %LOCALAPPDATA%\Programs\sne, adds
that folder to your PATH, and adds the setup line to your PowerShell profile. Set SNE_NO_MODIFY_PATH=1
or SNE_NO_PROFILE=1 first to skip either step, or SNE_VERSION=0.1.0 to pick a release.
If you prefer a wizard, download a setup program from the releases page. It does the same and adds an uninstaller. The installers are not code-signed yet, so Windows SmartScreen will ask you to confirm.
| Your Windows | Setup wizard | Portable (unzip and run) |
|---|---|---|
| 64-bit (most PCs) | sne-<version>-x64-setup.exe |
sne-<version>-x86_64-pc-windows-msvc.zip |
| ARM64 | sne-<version>-arm64-setup.exe |
sne-<version>-aarch64-pc-windows-msvc.zip |
With Scoop: scoop bucket add sne https://github.com/sne-sh/sne, then
scoop install sne.
The portable zip holds only sne.exe: put it anywhere and add the shell setup line below yourself.
There is no build for 32-bit Windows: Node.js stopped publishing one after version 22, and
sne 0.1.0-beta.5 was the last sne for it.
Windows PowerShell 5.1 blocks profile scripts by default. If the setup line does not run, allow local
scripts once with Set-ExecutionPolicy -Scope CurrentUser RemoteSigned.
Linux and macOS
|
It needs no root. It downloads the latest release, checks its SHA-256, puts sne in ~/.local/bin and
adds the setup lines to your bash, zsh or fish profile. Set SNE_INSTALL_DIR to change the folder,
SNE_NO_PROFILE=1 to leave your profile alone, or SNE_VERSION=0.1.0 to pick a release.
With Homebrew, on macOS or Linux; add the shell setup line below afterwards:
Packages are on the releases page too. These install sne
system-wide; add the shell setup line below afterwards.
| System | File | Install with |
|---|---|---|
| macOS (Intel and Apple silicon) | sne-<version>-macos-universal.pkg |
sudo installer -pkg <file> -target / |
| Debian, Ubuntu | sne_<version>_amd64.deb / _arm64.deb |
sudo dpkg -i <file> |
| Fedora, RHEL, openSUSE | sne-<version>-1.x86_64.rpm / .aarch64.rpm |
sudo rpm -i <file> |
| Any (portable) | sne-<version>-<target>.tar.gz |
unpack and put sne on your PATH |
The macOS package is not signed yet: use the command above, or right-click it in Finder and choose Open.
Every file is listed with its SHA-256 in SHA256SUMS.txt.
With a recent Rust toolchain, you can install from crates.io instead:
With npm, yarn, pnpm or bun, the package is sne-cli and the
command is sne. Read the
note about switching versions
first:
Or build from a clone of this repository:
Both put sne in ~/.cargo/bin. Add the shell setup line below afterwards.
Shell setup
install.ps1, the Windows setup wizard and install.sh do this for you. Otherwise add one line to your
profile:
| Shell | File | Line |
|---|---|---|
| bash | ~/.bashrc |
eval "$(sne env --use-on-cd)" |
| zsh | ~/.zshrc |
eval "$(sne env --use-on-cd)" |
| fish | ~/.config/fish/config.fish |
sne env --use-on-cd | source |
| PowerShell | $PROFILE |
sne env --use-on-cd | Out-String | Invoke-Expression |
| cmd | (per session) | FOR /f "tokens=*" %i IN ('sne env --shell cmd') DO CALL %i |
Leave out --use-on-cd if you do not want automatic switching when you enter a project.
Open a new terminal and run sne doctor to check the setup.
Usage
Short forms exist for the common commands: sne i 22, sne u 22, sne l, sne c, sne up, and sne -v for
the version. sne -h lists them all.
A version can be written as 22, 22.11, v22.11.0, latest, lts, lts/iron, a range such as
>=20 <23, or an alias.
Version files
When no version is given, and for automatic switching, sne looks in the current directory and then each parent for the first of:
.node-version.nvmrcpackage.jsonwith anengines.nodefield
With --use-on-cd, entering a project switches to its version if that version is installed and the
active one does not already satisfy the request. Leaving a project keeps the current version.
How it works
sne env runs once per shell. It creates a link in sne's data directory that points at the default
version's bin directory, and puts that link on PATH. From then on, sne use only re-points the link
(a symlink on Linux and macOS, a junction on Windows). Each shell has its own link, so different
terminals can use different versions.
Installs stream the archive from nodejs.org, hash it while it downloads, and unpack it into a temporary directory that is renamed into place only after the checksum matches. On Linux and macOS the archive is decompressed as it arrives and never written to disk; on Windows the zip is unpacked on several threads.
Configuration
| Variable | Purpose | Default |
|---|---|---|
SNE_DIR |
Where versions, aliases and the cache live | %LOCALAPPDATA%\sne on Windows, $XDG_DATA_HOME/sne or ~/.local/share/sne elsewhere |
SNE_NO_UPDATE_CHECK |
Set to 1 so sne install never looks for a new sne version |
not set |
SNE_NO_MODIFY_PATH |
Windows: set to 1 so sne use, sne default and sne install never add the default Node version to your PATH |
not set |
SNE_NODE_MIRROR |
Download mirror | https://nodejs.org/dist (musl Linux: https://unofficial-builds.nodejs.org/download/release) |
Performance
Measured on Windows 11 with the release build, averaged over 50 runs from PowerShell:
| Command | Time |
|---|---|
sne use 20 |
6.8 ms |
sne use --auto (the cd hook) |
6.1 ms |
sne env |
7.2 ms |
sne current |
5.9 ms |
starting an empty cmd /c exit, for scale |
8.9 ms |
Almost all of that is the cost of starting any process on Windows. Installing two Node versions in
parallel (sne install lts 20) took 2.4 s on a fast connection.
Run benches/bench.sh (needs hyperfine) to measure on your
machine; it also compares against fnm when fnm is installed.
Development
See CONTRIBUTING.md.
Privacy
sne connects to two places, and only for these reasons:
- nodejs.org (or the mirror in
SNE_NODE_MIRROR), to list and download Node.js versions. - GitHub, to look for a new version of sne: at most once a day while
sne installruns, when you runsne self checkorsne update, and every 4 hours if you turned onsne notify.
It sends nothing about you or your machine beyond what any download sends (your IP address and a
sne/<version> user agent). There is no telemetry and no account. SNE_NO_UPDATE_CHECK=1 stops the
check during sne install.
Code signing policy
The Windows installers and sne.exe are not code-signed yet, so Windows may warn before running
them. Every release file is listed with its SHA-256 in SHA256SUMS.txt and has a
build provenance record from the GitHub workflow that built it.
When signing starts, only files built by the release workflow in this repository from a tagged commit will be signed, and each signing will be approved by hand by a maintainer.
| Role | Who |
|---|---|
| Authors and reviewers | The maintainers of sne-sh/sne |
| Approvers of each release | The owners of the sne-sh organization |