TYtype0·Aug 28, 2017Submission
N – Interactively Manage Your Node.js Versions
1 points · Open discussiontj
n
Shell2011–2024
tj / n
n
Node version management
30Distinct people
31Mentions
0Explicit recommenders
19.5KGitHub stars
What to know before exploring
What it is
Node version management
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- nvm-sh/nvm · linked in 5 of the same discussions
- mklement0/n-install · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year31 dated mentions
Observed mentions: 2011-04-02 17:01:58 UTC to 2024-12-09 00:42:58 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesAnother way is to use "n": https://github.com/tj/n
In Node v8.0.0 ReleasedI've had way, way, way more problems deploying Node on all the various and fragmented *nix distros than Windows, since none of them match the dev environment 1:1 either.
As a matter of fact, just setting up Node on my dev machines is way simpler and easier on Windows when compared with Mac or Linux. It's the same on every Windows box - download the Node.js installer, run it. Done.
Meanwhile on Linux and Mac I have to jump through hoops and deal with things like package managers not being up to date, Brew getting broken after updates, lack of standards for installing apps, installs just not working, no easy upgrade path, etc.
Honestly, if I have to type out any commands to install stuff then the situation is already fucked. Commands that I don't run very often are subject to being forgotten. Then when I go to do an update, I have to rememb
Read the rest
er how I installed it in the first place or I have to find some tool to completely clean it off my system (or I have to use Node to update itself with something like https://github.com/tj/n, which was invented for this exact situation.)