菜单
Migrating from nvm to mise — reading .nvmrc, translating `nvm use` shell hooks, tearing down ~/.nvm cleanly, and handling the common bashrc/zshrc entries. Use when a user is currently using nvm and wants to adopt mise without losing their pinned Node versions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end recipe for a modern C++ project managed by mise — cmake + ninja + ccache + mold linker + clang-tools + optional conan package manager. Full CMakePresets.json, mise.toml tasks, and first-run walkthrough. Use when starting a new C++ project or modernizing an existing one.
End-to-end recipe for a Docker-based dev loop with mise — multi-stage Dockerfile with mise pre-installed, docker-compose for services (Postgres, Redis), BuildKit cache mounts, and mise tasks that wrap compose. Use when running dev entirely in containers or prod-parity testing.
End-to-end recipe for a Go HTTP service managed by mise — Go + air (hot reload) + golangci-lint + gotestsum + a Dockerfile hint for production. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Go service or adding mise to an existing one.
End-to-end recipe for a Neovim configuration managed by mise — the vim.env.PATH prepend pattern, LSPs installed via mise (npm:pyright, aqua:gopls, etc.), conform.nvim for formatters, and the mise-managed "editor as a tool" approach. Use when setting up a modern Neovim config that plays nicely with mise-managed projects.
End-to-end recipe for a Next.js app managed by mise — Node + pnpm (via corepack) + TypeScript + Prettier + ESLint + Playwright. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new Next.js app or adding mise to an existing one.
End-to-end recipe for a FastAPI service managed by mise — Python + uv + ruff + pytest + a Postgres env var. Complete mise.toml template, first-run walkthrough, and common gotchas. Use when starting a new FastAPI project or adding mise to an existing one.
| name | mise-migrate-from-nvm |
| description | Migrating from nvm to mise — reading .nvmrc, translating `nvm use` shell hooks, tearing down ~/.nvm cleanly, and handling the common bashrc/zshrc entries. Use when a user is currently using nvm and wants to adopt mise without losing their pinned Node versions. |
nvm is the default Node version manager most developers start with. It works but has two common pain points: slow shell startup (it's a big shell function, sourced on every new terminal) and no support for any language other than Node. mise fixes both.
mise.toml with the same Node version(s).mise activate.which node and versions match.Don't do the uninstall step until after verifying mise is working — it's reversible but inconvenient.
nvm ls # installed versions + current alias
cat ~/.nvm/alias/default # default version (if aliased)
cat .nvmrc # project version (if present)
grep -r nvm ~/.zshrc ~/.bashrc ~/.bash_profile 2>/dev/null # shell init
Note:
.nvmrc files in active projects.nvm use / nvm install commands in shell rc.mise.toml per projectFor each project that has a .nvmrc, create a mise.toml:
[tools]
node = "22.12.0" # value from .nvmrc
Or, enable idiomatic reading so mise reads .nvmrc directly (no mise.toml needed):
# mise.toml — or ~/.config/mise/config.toml for global
[settings]
idiomatic_version_file_enable_tools = ["node"]
With the idiomatic reader, an existing .nvmrc just works.
For your global default (the version you get with no project config), edit ~/.config/mise/config.toml:
[tools]
node = "lts" # or the specific version you had as nvm default
Remove nvm's init:
# ~/.zshrc — DELETE these lines
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"
Add mise's init:
# ~/.zshrc — ADD
eval "$(mise activate zsh)"
(For bash: eval "$(mise activate bash)" in ~/.bashrc or ~/.bash_profile.)
Restart the shell (exec zsh / exec bash / open a new terminal).
which node
# Should print something under ~/.local/share/mise/shims/ or ~/.local/share/mise/installs/
node --version
# Should print the version you set in mise.toml / global config
cd <project-with-.nvmrc>
node --version
# Should match the .nvmrc
If which node still points to ~/.nvm/..., the old nvm shim is still on PATH. Check for leftover nvm init lines, and confirm mise activate is the last thing run in your shell rc (so its PATH prepend wins).
Once mise is working reliably:
rm -rf "$HOME/.nvm"
unalias nvm 2>/dev/null
If you installed nvm via Homebrew: brew uninstall nvm.
Restart the shell. Run which nvm — should print "not found".
nvm use in scriptsIf you have shell scripts or Makefiles with nvm use in them, replace with mise:
# Before
nvm use 22
# After — mise auto-activates from mise.toml / .nvmrc in the cwd, so usually nothing needed.
# If you need to force a version in a script:
mise use --pin node@22
The mise.toml in the project's working directory is read automatically when mise is activated. In most scripts, just deleting the nvm use line is enough.
--install-latest and friends# nvm
nvm install --lts
# mise equivalent
mise use -g node@lts # install + set as global default
You removed nvm but the shell still has the nvm version on PATH from before. Open a fresh terminal — the new shell has mise's shims instead.
Check mise ls node — does it list the version you expect? If not, mise install node@<version> first.
Then check mise current in the project dir — it shows which version is active and which config file set it.
.nvmrc is ignoredEnable the idiomatic reader:
# ~/.config/mise/config.toml
[settings]
idiomatic_version_file_enable_tools = ["node"]
Or, add node = "<version>" explicitly to mise.toml.
If removing nvm didn't speed up your shell, something else is slow. time zsh -i -c exit to measure; profile with zsh -xv to find the culprit. mise itself adds <20ms on a modern machine.
Find: extensions, tools, or scripts that call nvm exec. Replace nvm exec with mise exec:
# Before
nvm exec 22 npm run build
# After
mise exec node@22 -- npm run build
mise supports multiple versions per tool:
[tools]
node = "24 22 20" # three concurrent installs; first is default
Same as nvm's multi-install, just with one command to install them all (mise install).
If you had npm install -g prettier etc., they lived in nvm's per-version dirs. mise has the same isolation — you need to reinstall globals after migrating. Or, better, switch to mise's npm: backend:
[tools]
node = "24"
"npm:prettier" = "latest"
"npm:typescript" = "latest"
This gets you pinned, lockfile-tracked global CLIs.
If you installed pnpm/yarn via npm install -g pnpm, switch to corepack + packageManager (see mise-lang-node-packages).
If mise isn't working out for some reason (unlikely):
# Reinstall nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.0/install.sh | bash
# Remove mise activation from shell rc, restart shell.
Your .nvmrc files are still there — nothing was deleted.
mise-lang-node-overview — Node version resolution in mise.mise-lang-node-packages — corepack + packageManager.mise-shell-activation — mise activate vs shims-on-PATH.mise-migrate-from-asdf — similar migration shape, for asdf users.mise.jdx.dev/faq.html#migrating-from-nvm.