You may have come across pnpm through discussions with fellow developers, reading blog posts, watching videos, or attending developer conferences. You have probably heard its praises: it's fast, disk-space efficient, and great for monorepos.
You have a dependency in your project and want to execute a command using it? The pnpm exec command can help you with that.
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.
Sometimes, all you want to do is grab an npm package and execute a command with it, without having to install it (whether globally or as a dependency).
This week, I installed .NET 7 on my laptop and I used Windows Package Manager for that:
In this article, I talked about my latest project: how I built a script to automate the setup of my developer machine using Boxstarter, Chocolatey, Winget, and PowerShell... and how I learned a few things along the way.
In my previous articles about winget I talked about installing packages but I did not talk about producing packages for Windows Package Manager. So let's set things right.
In my last article about Windows Package Manager, I said that with winget I was missing "being able to specify some parameters for a package installation (like the workload and components to install for Visual Studio 2019)". Well, that was before I went through a few GitHub issues of the winget-cli repository that mentioned the