![]() What I want to be able to do is name each version by customer. Alias allows you to refer to a version by a name of your choice. I saw that they had an option for creating an Alias which NVM for Windows did not. ![]() I looked into the available commands for NVM and NVM for Windows and immediately noticed that NVM has more. For a list of node versions that are compatible with SPFX, take a look at the SPFx Compat i bility Matrix, Note: v14.4.0 is used just for the purpose of setting up NPM and is not a supported version for SPFx development. Maybe you are inheriting a project that is running on a specific version of Node, then the above isn’t an option but you really want to keep the customer specific modules separate. For example, Contoso would run Node v14.4.0 while Fabrikam runs on Node v14.3.0. One way to separate the two would be to dedicate a minor version to a customer. As an example, let’s say I have a customer, Contoso, who wants to use Node v14.4.0 and Gulp.js while my other customer, Fabrikam, wants to use Node v14.4.0 and Grunt.js. In our conversation, we talked about the idea of isolating by customer. I had issues setting up the latest version of SPFx in Docker, but NVM seemed to be a great option. The hint is in the title of this post.įor SPFx development, I use Docker for isolation. In this post, I’ll talk about the 1 missing feature that I really wanted to use, and what I did to get it. The thing you find out right away when trying to use NVM for Windows is that it’s a separate project from NVM and it doesn’t have all the same features. I’m on a Windows machine so we talked about Node Version Manager for Windows since the original NVM was not written for Windows. The topic was using Node Version Manager (NVM) to handle different node versions on the same machine. A few nights ago, I sat in on a PnP Sharing is Caring call with David Warner II and Hugo Bernier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |