-
Notifications
You must be signed in to change notification settings - Fork 581
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 install failing. Symlink problems? #26
Comments
How did you try to install npm? |
It's what is on nodejs.org's site |
I've got a similar error when trying to install node and npm using nvm |
same thing here.
|
Using this I've had some luck installing some npm modules, but it still does have issues with permission errors whenever npm tries to rename a file. INSTALL GLOBAL NPM PACKAGES CLEAN CACHE BYPASS SYMLINK ISSUES |
What's odd is the |
In my tests, using pip, I was unable to create a virtualenv in my user folder.
But was able to create inside Ubuntu filesystem
|
I think you've got the ln -s backwards, mine created just fine inside bash |
I was unable to use
thanks nerdofsteel for the suggestions. I too ran into the rename issue when trying to globally install a module. The no symlinks option seems to work like a charm for my local dependencies. |
I think the problem for both virtualenv and npm is that those tools tries to create links to the Lxss filesystem.
|
It appears to be a problem with tar. It doesn't create symlinks ever. Every tool that I've tried to install that uses tar with symlinks fails. |
More info here: microsoft/WSL#3 |
Just |
$ npm install -g npm npm ERR! A complete log of this run can be found in: |
Thank. It's working:)) |
This worked like a charm! Thank you! |
In my case I mount vfat into media so my ubuntu can't create symlinks into that mount point and raise this kind of error. |
Fix the code if the deploy log in Netlify gives any error or warning and it will deploy. |
Thanks it worked...!! |
If you are using vs code, close it! |
I ran into symlink issues with weird relative paths: And now npm is borked, as the rollback failed... |
It's working... perfect |
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/local/bin/npm" "install"
npm ERR! node v4.4.2
npm ERR! npm v3.8.5
npm ERR! path ../mime/cli.js
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! syscall symlink
npm ERR! Error: EPERM: operation not permitted, symlink '../mime/cli.js' -> '/mnt/c/users/kyle/Documents/dev/listomaniapi/node_modules/.bin/mime'
npm ERR! at Error (native)
npm ERR! { [Error: EPERM: operation not permitted, symlink '../mime/cli.js' -> '/mnt/c/users/kyle/Documents/dev/listomaniapi/node_modules/.bin/mime']
npm ERR! errno: -1,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'symlink',
npm ERR! path: '../mime/cli.js',
npm ERR! dest: '/mnt/c/users/kyle/Documents/dev/listomaniapi/node_modules/.bin/mime',
npm ERR! parent: 'listomaniapi' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR! /mnt/c/users/kyle/Documents/dev/listomaniapi/npm-debug.log
npm ERR! code 1
root@localhost:~/dev/listomaniapi#
The text was updated successfully, but these errors were encountered: