Node-sass: keep getting error MSB4019 while installing node-sass

Created on 4 Jul 2018  Â·  9Comments  Â·  Source: sass/node-sass

Angular CLI: 6.0.8
Node: 8.11.3
OS: win32 x64
Angular: 5.2.11
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.6.8 (cli-only)
@angular-devkit/core 0.6.8 (cli-only)
@angular-devkit/schematics 0.6.8 (cli-only)
@schematics/angular 0.6.8 (cli-only)
@schematics/update 0.6.8 (cli-only)
rxjs 5.5.11
typescript 2.7.2
webpack 4.14.0

Not able to install the node-sass .. keep getting error MSB4019.
node-sass\build\src\libsass.vcxproj(20,3): error MSB4019: The imported project "C:\Microsoft.Cpp.
Default.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Can someone able to help on this?

Most helpful comment

@Narasinha, open Command Prompt as Administrator: [Win+x] -> Command Prompt (Admin) and run the following commands:

npm install -g --production windows-build-tools
set VCTargetsPath=%programfiles(x86)%\MSBuild\Microsoft.Cpp\v4.0\V140
npm install -g node-gyp

then try to install node-sass one more time.

All 9 comments

What version of node-sass are you trying to install?

On Wed., 4 Jul. 2018, 5:29 pm Narasinha, notifications@github.com wrote:

Angular CLI: 6.0.8
Node: 8.11.3
OS: win32 x64
Angular: 5.2.11
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version

@angular-devkit/architect 0.6.8 (cli-only)
@angular-devkit/core 0.6.8 (cli-only)
@angular-devkit/schematics 0.6.8 (cli-only)
@schematics/angular 0.6.8 (cli-only)
@schematics/update 0.6.8 (cli-only)
rxjs 5.5.11
typescript 2.7.2
webpack 4.14.0

Not able to install the node-sass .. keep getting error MSB4019.
node-sass\build\src\libsass.vcxproj(20,3): error MSB4019: The imported
project "C:\Microsoft.Cpp.
Default.props" was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.

Can someone able to help on this?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2433, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWJEpQk7Jg87siLn9JUj6UCDUxN-aks5uDG7ugaJpZM4VCFgP
.

I'm trying to install node-sass 4.9.0

Please provide the full install output as a github gist.

@Narasinha, open Command Prompt as Administrator: [Win+x] -> Command Prompt (Admin) and run the following commands:

npm install -g --production windows-build-tools
set VCTargetsPath=%programfiles(x86)%\MSBuild\Microsoft.Cpp\v4.0\V140
npm install -g node-gyp

then try to install node-sass one more time.

Or if using VS 2017 , path is "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets"

Node v10.15.0
npm 6.4.1

I also facing this issue now.

Aldready did.

npm install -g --production windows-build-tools
set VCTargetsPath=%programfiles(x86)%\MSBuild\Microsoft.Cpp\v4.0\V140
npm install -g node-gyp

Run admin, reinstall, change privillege of msbuild folder etc. Unlucky.

This node-sass package is the most common issue when I deploy or migrate the project. If its not the version then dependencies. You have to adjust by ur self just to run npm install. Everytime, so frustrating.

I was having similar issues when I was using Node 10.15.3, switched to 8.15.1 and it npm installed correctly.

The @generalov comment worked for me. Just make sure to close all consoles before trying to install node-sass again.

npm install node-sass
just write this instead of any version. it solved the problem for me!

Was this page helpful?
0 / 5 - 0 ratings