Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nvm to hold ring #74

Merged
merged 2 commits into from
Feb 21, 2024
Merged

Add nvm to hold ring #74

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
635148f
Add nvm to hold ring
gunzip Feb 21, 2024
7324d30
Merge branch 'main' into hold-nvm
gunzip Feb 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions radar/tools/nvm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "nvm"
ring: hold
quadrant: "tools"
tags: [typescript, nodejs, javascript]
---

[nvm](https://https://github.com/nvm-sh/nvm) is a version manager for node.js,
designed to be installed per-user, and invoked per-shell. It is a common tool
for managing multiple versions of Node.js and is used by many developers.

Despite we've used it in the past, we are not using it anymore since we've
replaced it with [nodenv](https://github.com/nodenv/nodenv) which offers a
similar functionality but it's more flexible and maintained.

We observed that nodenv has a minimal impact on system performance (i.e. doesn't
freeze zsh shell when switching between directories) and offers [greater
flexibility](https://github.com/nodenv/nodenv/wiki/Why-nodenv%3F) in configuring
development environments.
Loading