Npm install error linux

npm install failing. Symlink problems? #26

Comments

Sparticuz commented Apr 7, 2016

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:

The text was updated successfully, but these errors were encountered:

cowens commented Apr 7, 2016

How did you try to install npm?

Sparticuz commented Apr 7, 2016

curl -sL https://deb.nodesource.com/setup_4.x | bash —
apt-get install nodejs

It’s what is on nodejs.org’s site

filipeaguiar commented Apr 7, 2016

I’ve got a similar error when trying to install node and npm using nvm

ThaJay commented Apr 7, 2016

same thing here.
A subdependency would love to make a symlink, and npm i fails because it can’t.
We have symlinks in cmd through mklink /J so I don’t really get why it’s not possible through WSL yet.

therocco commented Apr 7, 2016

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
npm config set unsafe-perm true

CLEAN CACHE
npm cache clean

BYPASS SYMLINK ISSUES
npm install —no-bin-links

Sparticuz commented Apr 7, 2016

We have symlinks in cmd through mklink /J so I don’t really get why it’s not possible through WSL yet.

What’s odd is the ln -s seems to work fine

sergiogarciadev commented Apr 7, 2016

In my tests, using pip, I was unable to create a virtualenv in my user folder.

But was able to create inside Ubuntu filesystem

Sparticuz commented Apr 7, 2016

I think you’ve got the ln -s backwards, mine created just fine inside bash
lrwxrwxrwx 1 root root 31 Apr 7 01:24 dev -> /mnt/c/users/kyle/Documents/dev/

ThaJay commented Apr 8, 2016

I was unable to use ln -s on /mnt/c/ (Operation not permitted) but it did work for me in the unix filesystem, for instance at

/ . a symlink created through mklink /J in cmd showed up in my bash, but it did look a bit strange (same for normal mklink ):

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.

sergiogarciadev commented Apr 8, 2016

I think the problem for both virtualenv and npm is that those tools tries to create links to the Lxss filesystem.

filipeaguiar commented Apr 9, 2016

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.

Sparticuz commented Apr 12, 2016

ale0sx commented Jan 13, 2018

Just sudo npm install -g npm@5.3.0

aswathykrishna18 commented Jan 16, 2018

$ npm install -g npm
C:\Users\aswathy\AppData\Roaming\npm\npx -> C:\Users\aswathy\AppData\Roaming\npm\node_modules\npm\bin\npx-cli.js
npm ERR! path C:\Users\aswathy\AppData\Roaming\npm\npm
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall open
npm ERR! Error: EPERM: operation not permitted, open ‘C:\Users\aswathy\AppData\Roaming\npm\npm’
npm ERR! < Error: EPERM: operation not permitted, open 'C:\Users\aswathy\AppData\Roaming\npm\npm'
npm ERR! cause:
npm ERR! < Error: EPERM: operation not permitted, open 'C:\Users\aswathy\AppData\Roaming\npm\npm'
npm ERR! errno: -4048,
npm ERR! code: ‘EPERM’,
npm ERR! syscall: ‘open’,
npm ERR! path: ‘C:\Users\aswathy\AppData\Roaming\npm\npm’ >,
npm ERR! stack: ‘Error: EPERM: operation not permitted, open ‘C:\Users\aswathy\AppData\Roaming\npm\npm»,
npm ERR! errno: -4048,
npm ERR! code: ‘EPERM’,
npm ERR! syscall: ‘open’,
npm ERR! path: ‘C:\Users\aswathy\AppData\Roaming\npm\npm’ >
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\aswathy\AppData\Roaming\npm-cache_logs\2018-01-16T10_46_38_513Z-debug.log

racibaz commented May 29, 2020

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
npm config set unsafe-perm true

CLEAN CACHE
npm cache clean

BYPASS SYMLINK ISSUES
npm install —no-bin-links

Thank. It’s working:))

aqeebimtiaz commented May 29, 2020

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
npm config set unsafe-perm true

CLEAN CACHE
npm cache clean

BYPASS SYMLINK ISSUES
npm install —no-bin-links

This worked like a charm! Thank you!

razonklnbd commented Oct 18, 2020

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.

ShivanshSharma1 commented Nov 3, 2020

Fix the code if the deploy log in Netlify gives any error or warning and it will deploy.

CodeWithHiteshYT commented Dec 4, 2020

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
npm config set unsafe-perm true

CLEAN CACHE
npm cache clean

BYPASS SYMLINK ISSUES
npm install —no-bin-links

Thanks it worked.

Dragonphy commented May 18, 2021

If you are using vs code, close it!

killroy42 commented Jun 29, 2021

I ran into symlink issues with weird relative paths:
Error: EACCES: permission denied, symlink ‘../../../lib/node_modules/npm/man/man5/npm-shrinkwrap-json.5’ -> ‘/usr/share/man/man5/npm-shrinkwrap-json.5’

And now npm is borked, as the rollback failed.

Источник

NPM Error installing on Ubuntu #4

Comments

jpontius commented Nov 1, 2014

uname -a
Linux justin-Latitude-D620 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty

ffmpeg version 1.2.6-7:1.2.6-1 trusty1 Copyright (c) 2000-2014 the FFmpeg developers
built on Apr 26 2014 18:52:58 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
configuration: —arch=amd64 —disable-stripping —enable-avresample —enable-pthreads —enable-runtime-cpudetect —extra-version=’7:1.2.6-1 trusty1′ —libdir=/usr/lib/x86_64-linux-gnu —prefix=/usr —enable-bzlib —enable-libdc1394 —enable-libfreetype —enable-frei0r —enable-gnutls —enable-libgsm —enable-libmp3lame —enable-librtmp —enable-libopencv —enable-libopenjpeg —enable-libopus —enable-libpulse —enable-libschroedinger —enable-libspeex —enable-libtheora —enable-vaapi —enable-vdpau —enable-libvorbis —enable-libvpx —enable-zlib —enable-gpl —enable-postproc —enable-libcdio —enable-x11grab —enable-libx264 —shlibdir=/usr/lib/x86_64-linux-gnu —enable-shared —disable-static
libavutil 52. 18.100 / 52. 18.100
libavcodec 54. 92.100 / 54. 92.100
libavformat 54. 63.104 / 54. 63.104
libavdevice 53. 5.103 / 53. 5.103
libavfilter 3. 42.103 / 3. 42.103
libswscale 2. 2.100 / 2. 2.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 2.100 / 52. 2.100

node —version
v0.10.25

npm —version
1.3.10

NPM Debug Log:
9825 silly lockFile 652c89fc—justin-npm-co-3-1-0-package-tgz tar:///home/justin/.npm/co/3.1.0/package.tgz
9826 verbose lock tar:///home/justin/.npm/co/3.1.0/package.tgz /home/justin/.npm/652c89fc—justin-npm-co-3-1-0-package-tgz.lock
9827 silly gunzTarPerm modes [ ‘755’, ‘644’ ]
9828 error Error: No compatible version found: mdns-js@’shahriman/node-mdns-js’
9828 error Valid install targets:
9828 error [«0.0.1″,»0.0.2″,»0.0.3″,»0.0.5″,»0.0.6″,»0.1.0″,»0.1.1″,»0.1.2″,»0.1.3»]
9828 error at installTargetsError (/usr/share/npm/lib/cache.js:719:10)
9828 error at /usr/share/npm/lib/cache.js:638:10
9828 error at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
9828 error at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
9828 error at Object.oncomplete (fs.js:107:15)
9829 error If you need help, you may report this log at:
9829 error http://github.com/isaacs/npm/issues
9829 error or email it to:
9829 error npm-@googlegroups.com
9830 error System Linux 3.13.0-24-generic
9831 error command «/usr/bin/nodejs» «/usr/bin/npm» «install» «castnow» «-g»
9832 error cwd /home/justin
9833 error node -v v0.10.25
9834 error npm -v 1.3.10
9835 verbose exit [ 1, true ]

The text was updated successfully, but these errors were encountered:

Источник

Как разобраться с npm?

Проблема с npm, при установке например: npm install node-sass
Останавливается на этом: normalize tree sill install loadcurrenttree

• Вопрос задан более трёх лет назад
• 1377 просмотров

Александр +: Никита Полевой: SM:
я прокси удалил.
npm config delete http-proxy
npm config delete https-proxy
npm config rm proxy
npm config rm https-proxy
set HTTP_PROXY=null
set HTTPS_PROXY=null

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/nodejs’,
1 verbose cli ‘/usr/bin/npm’,
1 verbose cli ‘install’,
1 verbose cli ‘-g’,
1 verbose cli ‘cordova’,
1 verbose cli ‘ionic’ ]
2 info using npm@3.5.2
3 info using node@v4.2.6
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly fetchPackageMetaData cordova
8 silly fetchPackageMetaData ionic
9 silly fetchNamedPackageData cordova
10 silly mapToRegistry name cordova
11 silly mapToRegistry using default registry
12 silly mapToRegistry registry https://your.registry.url/
13 silly mapToRegistry uri https://your.registry.url/cordova
14 verbose request uri https://your.registry.url/cordova
15 verbose request no auth needed
16 info attempt registry request try #1 at 12:18:18
17 verbose request id ed3b078ddd449fde
18 http request GET https://your.registry.url/cordova
19 silly fetchNamedPackageData ionic
20 silly mapToRegistry name ionic
21 silly mapToRegistry using default registry
22 silly mapToRegistry registry https://your.registry.url/
23 silly mapToRegistry uri https://your.registry.url/ionic
24 verbose request uri https://your.registry.url/ionic
25 verbose request no auth needed
26 info attempt registry request try #1 at 12:18:18
27 http request GET https://your.registry.url/ionic
28 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
29 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
30 info attempt registry request try #2 at 12:18:28
31 http request GET https://your.registry.url/cordova
32 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
33 info attempt registry request try #2 at 12:18:28
34 http request GET https://your.registry.url/ionic
35 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
36 info attempt registry request try #3 at 12:19:28
37 http request GET https://your.registry.url/cordova
38 silly fetchPackageMetaData Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
38 silly fetchPackageMetaData at ClientRequest.onError (/usr/share/npm/node_modules/request/node_modules/tunnel-agent/index.js:174:17)
38 silly fetchPackageMetaData at ClientRequest.g (events.js:260:16)
38 silly fetchPackageMetaData at emitOne (events.js:77:13)
38 silly fetchPackageMetaData at ClientRequest.emit (events.js:169:7)
38 silly fetchPackageMetaData at Socket.socketErrorListener (_http_client.js:258:9)
38 silly fetchPackageMetaData at emitOne (events.js:77:13)
38 silly fetchPackageMetaData at Socket.emit (events.js:169:7)
38 silly fetchPackageMetaData at connectErrorNT (net.js:998:8)
38 silly fetchPackageMetaData at nextTickCallbackWith2Args (node.js:441:9)
38 silly fetchPackageMetaData at process._tickCallback (node.js:355:17)
38 silly fetchPackageMetaData error for cordova < [Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80] code: 'ECONNRESET' >
39 info attempt registry request try #3 at 12:19:28
40 http request GET https://your.registry.url/ionic
41 silly fetchPackageMetaData Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
41 silly fetchPackageMetaData at ClientRequest.onError (/usr/share/npm/node_modules/request/node_modules/tunnel-agent/index.js:174:17)
41 silly fetchPackageMetaData at ClientRequest.g (events.js:260:16)
41 silly fetchPackageMetaData at emitOne (events.js:77:13)
41 silly fetchPackageMetaData at ClientRequest.emit (events.js:169:7)
41 silly fetchPackageMetaData at Socket.socketErrorListener (_http_client.js:258:9)
41 silly fetchPackageMetaData at emitOne (events.js:77:13)
41 silly fetchPackageMetaData at Socket.emit (events.js:169:7)
41 silly fetchPackageMetaData at connectErrorNT (net.js:998:8)
41 silly fetchPackageMetaData at nextTickCallbackWith2Args (node.js:441:9)
41 silly fetchPackageMetaData at process._tickCallback (node.js:355:17)
41 silly fetchPackageMetaData error for ionic < [Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80] code: 'ECONNRESET' >
42 silly rollbackFailedOptional Starting
43 silly rollbackFailedOptional Finishing
44 silly runTopLevelLifecycles Starting
45 silly runTopLevelLifecycles Finishing
46 silly install printInstalled
47 verbose stack Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
47 verbose stack at ClientRequest.onError (/usr/share/npm/node_modules/request/node_modules/tunnel-agent/index.js:174:17)
47 verbose stack at ClientRequest.g (events.js:260:16)
47 verbose stack at emitOne (events.js:77:13)
47 verbose stack at ClientRequest.emit (events.js:169:7)
47 verbose stack at Socket.socketErrorListener (_http_client.js:258:9)
47 verbose stack at emitOne (events.js:77:13)
47 verbose stack at Socket.emit (events.js:169:7)
47 verbose stack at connectErrorNT (net.js:998:8)
47 verbose stack at nextTickCallbackWith2Args (node.js:441:9)
47 verbose stack at process._tickCallback (node.js:355:17)
48 verbose cwd /home/djabrail
49 error Linux 4.4.0-38-generic
50 error argv «/usr/bin/nodejs» «/usr/bin/npm» «install» «-g» «cordova» «ionic»
51 error node v4.2.6
52 error npm v3.5.2
53 error code ECONNRESET
54 error network tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy_host proxy_host:80
55 error network This is most likely not a problem with npm itself
55 error network and is related to network connectivity.
55 error network In most cases you are behind a proxy or have bad network settings.
55 error network
55 error network If you are behind a proxy, please make sure that the
55 error network ‘proxy’ config is set properly. See: ‘npm help config’
56 verbose exit [ 1, true ]

Как всё запущено. Пациент скорее мёртв чем жив.

Источник