
I am a software developer living in Bordeaux. I am a .NET and Azure enthusiast, primarly coding in C# but I like to discover other languages and technologies too.
Search for a command to run...

I am a software developer living in Bordeaux. I am a .NET and Azure enthusiast, primarly coding in C# but I like to discover other languages and technologies too.
No comments yet. Be the first to comment.
Using Azure OpenID Connect with Pulumi in GitHub Actions

pnpm audit

Discussion about pnpm usage and popularity.

pnpm outdated

Why are we talking about CI in the first place? When working on a project, you typically focus on a specific feature at a time, making changes on a dedicated branch for that feature. When it's time for you to integrate these modifications into the pr...

Bordeaux Coders
10 posts
If you are working on various projects, you have likely encountered situations where you need to have multiple versions of Node.js installed on your computer.
You might not know it, but managing multiple Node.js versions is something you can do with pnpm, using the pnpm env command.
pnpm env use -g lts
This example demonstrates how to install the LTS version of Node.js.
Additionally, you can install specific versions of Node.js, view the versions already present on your computer, or remove one.
Because managing your Node.js version is built into pnpm: if you already use pnpm as your npm package manager, you don't need to install another tool.
But there is absolutely nothing wrong with using another Node version manager if you prefer. I was using nvm-windows before and I was happy with it. I just don't see the point of installing it anymore as similar functionality is already available in pnpm.
To specify a Node.js version to use in a project/folder, you can add an .npmrc file use-node-version setting, like that:
use-node-version=16.16.0