Skip to content

🚀 Expand Version Manager Examples in Version Check Message #133

Open
@Eric-Johnson-1

Description

@Eric-Johnson-1

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions