Npm ERR! gyp verb cli '-libsass_library='
Npm ERR! gyp verb cli '-libsass_ldflags=', Npm ERR! gyp verb cli '-libsass_cflags=', Npm ERR! gyp verb cli 'D:\MyProject\guigu-oa-parent\zguigu-oa-vue\guigu-oa-web\node_modules\node-gyp\bin\node-gyp.js', Npm ERR! gyp verb cli 'D:\nodejs\node.exe', Npm ERR! gyp info it worked if it ends with ok
Npm ERR! Building: D:\nodejs\node.exe D:\MyProject\guigu-oa-parent\zguigu-oa-vue\guigu-oa-web\node_modules\node-gyp\bin\node-gyp.js rebuild -verbose -libsass_ext= -libsass_cflags= -libsass_ldflags= -libsass_library= Npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js Npm ERR! path D:\MyProject\guigu-oa-parent\zguigu-oa-vue\guigu-oa-web\node_modules\node-sass Please, upgrade your dependencies to the actual version of core-js. Some versions have web compatibility issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Here is the changelog from github reposition, where you can check available versions and the differences.Npm WARN deprecated is no longer maintained and not recommended for usage due to the number of issues. So I guess the only way to know what angular-cli version should be installed is to try various versions, create a new project and checkout the package.json to see which angular version is used. NOTE: I have not found any page displaying the compatibility matrix of angular and angular-cli. The resulting white app will be created in the desired angular version. Install an angular-cli specific version npm install -g 2] Create a project ng new you-app-name npm uninstall -g run (-force flag might be required) npm cache clean If you're not sure of the angular-cli version installed in your environment, uninstall it. So getting the correct angular-cli version will lead you to getting the desired angular version.įrom that assumption, your question is not about angular-cli, but about npm. To answer your question, let's assume that you are interested in a specific angular version and NOT in a specific angular-cli version (angular-cli is just a tool after all).Ī reasonnable move is to keep your angular-cli version alligned with your angular version, otherwise you risk to stumble into incompatibilities issues.
0 kommentar(er)
