I don’t recommend going through this, but this is what I experienced and having the errors will help people find this article and get help faster. I think it’s worth trying Node 16 (or newer first) then downgrading if you need to. I uninstalled and installed Node 14.18.2 and it worked.
Npm install -g angular-cli fails again with this error npm ERR! LINK : fatal error LNK1181: cannot open input file 'DelayImp.lib' Note: I then installed Node 16 and the build tools install Visual Studio 2019 Build tools, but the PowerShell prompt didn’t seem like it finished for me. I uninstalled Node 16 and installed Node 14, checking the option to install extras, run through the admin command prompts and installs. Here’s how I solved it at after all my attempts. Maybe it’s easier to just install Visual Studio? I didn’t want to have to ask for a license and wanted to learn how to use VS Code well.
I didn’t get the environment paths set for me and this caused me a lot of problems, but I feel like a glossed through this step and that caused my problems. which will install Python2 and the VS 2017 Build tools needed, then npm install -g angular-cli. The easy way should be to install Node with the Windows installer, which includes the build tools (according to Npm install -g angular-cli The Easy Way should be Today (Jan 5, 2022), it’s trying to install. Unfortunately there's still a lot of tooling and system dependencies that require python 2." ~Dakota "node-sass has some of the worst requirements and breaking dependencies. I learned that node-sass requires Python 2 installed (even though it’s out of support, with a exe filename change) and msbuild.exe (in this case, I’m going all VS Code without Visual Studio). That has proved more difficult than I expected. In order to run the tests with ng test I need the Angular CLI. In this case, I get to work on an existing Angular project. I’m used to having Visual Studio installed, but was I get to start a new contract with a brand new, fast laptop! Hurray! Installing Angular-cli on a new machine without Visual Studio
0 kommentar(er)
