
If you’re planning on checking out or committing code to GitHub, you’ll also want tools for that: scoop install openssh git If your project uses Yarn, as ours does, you can grab that from Scoop, as well: scoop install yarn For just Node.js, you’ll want the nodejs package, plus nvm for version management with NVM: scoop install nodejs nvm Once you’ve got Scoop installed, it’s time to add some packages. Instead, install Scoop first, and you’ll get a nice, clean way to add the packages you’ll need without a single web search.

No one wants to waste time hunting down downloads for a development environment. In this post, I’ll talk you through how we get our Windows command-line environments set up for the Node.js (actually, Electron) application my team is developing. And, of course, with Node.js itself being constantly under development, you’ll want to lock down your development to a version your code can use. But if you need to compile extensions, you’ll need a few more things. Well, for some applications, that’s true. Node.js is just JavaScript, right? So it should be really easy to run Node.js applications on Windows-just download and install Node, npm install, and go, right?
