-
Notifications
You must be signed in to change notification settings - Fork 263
Open
Description
Issue Description
In our version-check.js, we tease two version managers (n and nvm) but only show love to n π
Let's give nvm its moment in the spotlight!
Current Situation
console.log(
chalk.yellow(
"Alternatively, we recommend using version managers like 'n' or 'nvm' to manage Node.js versions:"
)
);
console.log(
chalk.yellow(
"β’ n: npm install -g n (https://www.npmjs.com/package/n)"
)
);Proposed Change
Update the version check message to include installation instructions for both n and nvm:
console.log(
chalk.yellow(
"Alternatively, we recommend using version managers like 'n' or 'nvm' to manage Node.js versions:"
)
);
console.log(
chalk.yellow(
"β’ n: npm install -g n (https://www.npmjs.com/package/n)"
)
);
console.log(
chalk.yellow(
"β’ nvm: Check https://github.com/nvm-sh/nvm#installing-and-updating for the most up-to-date installation command"
)
);π€ Why This Matters
- Equal representation for version managers! π³οΈβπ
- Provide more comprehensive guidance for developers
- Show that we care about user choice and flexibility
π‘ Additional Context
Some developers prefer nvm, especially in cross-platform environments. Let's make sure they feel the love too!
π Fun Fact
Choosing a version manager is like choosing a pizza topping - personal preference matters! π
Is this a bug? Nope. Is it an improvement? Absolutely! π
Metadata
Metadata
Assignees
Labels
No labels