-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPM error while installing can-validate #31
Comments
I'm not much of a "systems" guy but does this line
mean Windows 10? We should be able to install it on any machine but I haven't tried it on any Windows machine. I'll have to locate a Windows 10 machine and debug from there.
I'm uncertain why |
You can get prebuilt VM images for Windows 10 directly from Microsoft; they're intended for testing IE/Edge versions but I don't see why you couldn't use them for node builds. https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/mac/ |
I am experiencing the same issue on Windows 8.1. Any ideas? Could it have something to do with that pipe character (|)? update: I also tested on a Windows 7 machine with the same result. Also have to mention that in both OS versions the following error is also shown:
|
Currently, I deleted node_modules folder and did an NPM install and I get this error.
C:\Users\santo\Workspace\workspace>npm install
npm WARN package.json logging@1.0.0 No repository field.
npm ERR! tar.unpack untar error C:\Users\santo\AppData\Roaming\npm-cache\can-validate\0.9.2\package.tgz
npm WARN optional dep failed, continuing fsevents@1.0.12
npm WARN deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated babel-core@5.8.14: Babel 5 is no longer being maintained. Upgrade to Babel 6.
WARN engine hawk@0.10.2: wanted: {"node":"0.8.x"} (current: {"node":"4.3.1","npm":"2.14.12"})
WARN engine boom@0.3.8: wanted: {"node":"0.8.x"} (current: {"node":"4.3.1","npm":"2.14.12"})
WARN engine cryptiles@0.1.3: wanted: {"node":"0.8.x"} (current: {"node":"4.3.1","npm":"2.14.12"})
WARN engine sntp@0.1.4: wanted: {"node":"0.8.x"} (current: {"node":"4.3.1","npm":"2.14.12"})
WARN engine hoek@0.7.6: wanted: {"node":"0.8.x"} (current: {"node":"4.3.1","npm":"2.14.12"})
npm WARN deprecated line-numbers@0.2.0: Copy its ~20 LOC directly into your code instead.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! path C:\Users\santo\Workspace\workspace-adminModule\admin-console\node_modules\can-validate\docs\can-validate-plugin|changelog.html
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\santo\Workspace\workspace-adminModule\admin-console\node_modules\can-validate\docs\can-validate-plugin|changelog.html'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
Note: https://github.com/canjs/can-validate/blob/master/changelog.html
not able to open this file.
The text was updated successfully, but these errors were encountered: