npm is no ok
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
C:\Users\Sean\Dropbox\nodejs\node_modules\sqlite3\build\deps\sqlite3\sqlite3.vcxproj(1,682): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. | |
ERR! Error: `C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe` failed with exit code: 1 | |
at ChildProcess.onExit (C:\Users\Sean\Dropbox\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:209:23) | |
at ChildProcess.emit (events.js:70:17) | |
at maybeExit (child_process.js:362:16) | |
at Process.onexit (child_process.js:398:5) | |
ERR! not ok | |
npm ERR! sqlite3@2.1.3 install: `node-gyp rebuild` | |
npm ERR! `cmd "/c" "node-gyp rebuild"` failed with 1 | |
npm ERR! | |
npm ERR! Failed at the sqlite3@2.1.3 install script. | |
npm ERR! This is most likely a problem with the sqlite3 package, | |
npm ERR! not with npm itself. | |
npm ERR! Tell the author that this fails on your system: | |
npm ERR! node-gyp rebuild | |
npm ERR! You can get their info via: | |
npm ERR! npm owner ls sqlite3 | |
npm ERR! There is likely additional logging output above. | |
npm ERR! | |
npm ERR! System Windows_NT 6.1.7601 | |
npm ERR! command "C:\\Users\\Sean\\Dropbox\\nodejs\\\\node.exe" "C:\\Users\\Sean\\Dropbox\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "sqlite3" | |
npm ERR! cwd C:\Users\Sean\Dropbox\nodejs | |
npm ERR! node -v v0.6.18 | |
npm ERR! npm -v 1.1.21 | |
npm ERR! code ELIFECYCLE | |
npm ERR! message sqlite3@2.1.3 install: `node-gyp rebuild` | |
npm ERR! message `cmd "/c" "node-gyp rebuild"` failed with 1 | |
npm ERR! errno {} | |
npm ERR! | |
npm ERR! Additional logging details can be found in: | |
npm ERR! C:\Users\Sean\Dropbox\nodejs\npm-debug.log | |
npm not ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment