![]() ![]() ![]() If you work in an environment where the computers are locked down or they do not want you messing with anything in Program Files.You want a single point of access for tools and configurations that can be used by multiple accounts on one machine.This approach has its advantages that have worked well for me which I will discuss below. We are going to walk through installing and configuring NVM for Windows in a non-default location. I’m also going to start off by saying this: If you are the only user on your machine and your account has administrator privileges, you can install NVM for Windows with either the default settings or how we will do it below and it will function the same way. This will allow you to easily switch between developing solutions for SharePoint Server 2019 and SharePoint Online due to the fact that the on-premises version of SharePoint requires you to use older versions of node. I highly recommend using NVM for Windows for all of my SharePoint Framework (SPFx) developers out there. The catch for NVM is that it only works on POSIX-compliant shells (sh, dash, ksh, zsh, bash), on UNIX, macOS, and Windows WSL (Windows Subsystem for Linux).Īll jokes aside, if you are developing on a Windows machine, you still have options! Additional options include setting up Windows WSL and installing NVM under whichever distro you choose (that will be a topic for another blog post), or you could use a similar but different application called NVM for Windows. It also provides tooling that lets you easily switch between different versions. It allows you to have several versions of node installed on your machine. ![]() If you have worked with node.js then you may be familiar with node version manager (NVM). This post will be a guide to install NVM for Windows if you want to use it with multiple user accounts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |