corepack VS nvm

I'd love to use Bun for my projects, but it's not integrated into Corepack yet (and therefore you cannot pin the bun version w/ checksum in package.json)

https://github.com/nodejs/corepack/issues/295

Recently Node 16 LTS cycle started. One month and a few days before the carry-over, a super controversial package titled `coredeps` [0] was officially declared a core module and has been bundled with all official distributions since.

The NodeJS team refuses to discuss NPM because it's a separate 3rd party. And yet.... this NodeJS Core module comes pre-installed as a global NPM package.

We're just getting started.

This module installs or even reinstalls any supported package manager when you execute a script with a name that would match any that they'd recognise. Opt-in for only a short period, and intending to expand beyond package manager installations.

Amidst all that's been going on, NPM (Nonstop Published Moments) is working on a feature that silently hijacks user commands and installs foreign software. The code found in those compromised packages operated in a similar manner and was labeled a critical severity vulnerability.

The following might actually make you cry.

Of these third party remote distributions it's downloading, the number of checksum, keys, or even build configurations that are being verified is 0.

The game that Microsoft is playing with their recent acquisitions here is quite clear, but there's too much collateral damage.

[0] https://github.com/nodejs/corepack#readme

The new Node.js LTS v16 will be released at the end of October (without a fancy name assigned yet), it'll have Corepack preinstalled in the default configuration since v16.9.0. 👌

Corepack integration

Hopefully you use nvm.

I am a javascript kind of guy, so I install nvm first.

O NPM instalado. Você pode baixá-lo em nodejs.org ou utilizar o NVM (Node version manager).

We actively use environment managers pyenv, goenv and nvm for managing multiple versions of Python, Golang and NodeJS at Mantis. These provide us with an easily manageable, robust development environments.

If you ever find yourself juggling different versions of Node.js for various projects, I highly recommend using NVM (Node Version Manager). It's a simple tool that makes switching between Node.js versions super easy. Whether you're working on older projects or testing new features, NVM lets you manage multiple versions without any hassle. It’s been a real lifesaver for me. For installation and more detail check nvm repo.

If you haven't already installed TxMS, you'll need Node.js installed. I recommend using nvm for Mac users. Once you've finished installing Node.js, proceed to the next step.

Official NVM Documentation — a complete guide to installing and using NVM.

On OSX, when it comes to managing version of things in NodeJS world, there are many options nvm, n, nodenv, volta, homebrewfor NodeJS management and other heap for package manager versions.

I also need to keep different versions of Node.js due to the accumulation of projects of varying ages over the years, plus old habits die hard. For convenient work, I recommend installing NVM, a version manager for Node.js.