Develop Reference

docker build problem with npm install Error: Invalid response body while trying to fetch https://registry.npmjs.org Socket timeout

docker build problem with npm install and it's only inside docker I've tested. it's working on my os perfectly
Error
Step 6/8 : RUN npm cache clear --force && npm install --legacy-peer-deps
---> Running in 361c2a07ac22
npm WARN using --force Recommended protections disabled.
npm notice
npm notice New minor version of npm available! 8.4.1 -> 8.5.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.5.0>
npm notice Run `npm install -g npm#8.5.0` to update!
npm notice
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/styled-jsx: Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-02-17T07_12_06_500Z-debug-0.log
The command '/bin/sh -c npm cache clear --force && npm install --legacy-peer-deps' returned a non-zero code: 1
docker file
FROM node:alpine
WORKDIR /app
ENV PORT 3000
COPY ./package.json /app/
COPY ./.npmrc ~
RUN npm cache clear --force && npm install --legacy-peer-deps
COPY . /app/
CMD ["npm", "start"]
as u can see I have added .npmrc file because I have read it somewhere but it didn't work or add npm cache clear --force so what should I do?

What version of Node your app is using? And what version of node you have installed on your OS?
You can check it using:
node -v
This image you used node:alpine is the newest version of the node, currently it's 17. So maybe you should use older one (the one you actualy have in your app).
You can find correct image on Docker Hub

How do I fix the npm install on Linux?

I'm trying to use npm install to install a package but I keep getting below error.
I tried updating and downloading again from root but nothing seems to work.
hackathonday1-2 git:(save-button) ✗ npm install file-saver --save
npm WARN checkPermissions Missing write access to
/home/salman/node_modules/axios npm WARN checkPermissions Missing
write access to /home/salman/node_modules/coffeescript npm WARN
checkPermissions Missing write access to
/home/salman/node_modules/coffee-script npm WARN checkPermissions
Missing write access to /home/salman/node_modules/file-saver npm WARN
checkPermissions Missing write access to
/home/salman/node_modules/materialize-css npm WARN enoent ENOENT: no
such file or directory, open '/home/salman/package.json' npm WARN
salman No description npm WARN salman No repository field. npm WARN
salman No README data npm WARN salman No license field.
npm ERR! code EACCES npm ERR! syscall access npm ERR! path
/home/salman/node_modules/axios npm ERR! errno -13 npm ERR! Error:
EACCES: permission denied, access '/home/salman/node_modules/axios'
npm ERR! [Error: EACCES: permission denied, access
'/home/salman/node_modules/axios'] { npm ERR! stack: "Error: EACCES:
permission denied, access '/home/salman/node_modules/axios'", npm ERR!
errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access',
npm ERR! path: '/home/salman/node_modules/axios' npm ERR! } npm ERR!
npm ERR! The operation was rejected by your operating system. npm ERR!
It is likely you do not have the permissions to access this file as
the current user npm ERR! npm ERR! If you believe this might be a
permissions issue, please double-check the npm ERR! permissions of the
file and its containing directories, or try running npm ERR! the
command again as root/Administrator.
npm ERR! A complete log of this run can be found in: npm ERR!
/home/salman/.npm/_logs/2019-09-24T03_37_30_909Z-debug.log

If there is a permission error on Linux for npm install, you can try to include sudo at the beginning of command. sudo npm install. Also make sure node.js is installed globally on your machine. Also make sure you have a package.json folder.

It's simply complaining about the fact that you don't own the folders /home/salman/node_modules/axios, /home/salman/node_modules/file-saver etc. Since it is your home directory, there really shouldn't be any directory or files that you don't own in /home/salman. My guess is that this happened because you ran npm with sudo causing it to create some files in your home folder that is owned by root instead of salman.
To fix the permission issue simply retake ownership of the node_modules folder:
cd /home/salman
sudo chown -R salman:salman node_modules
The -R flag makes chown recursively set you as the owner to all files and subfolders in the directory.
Side note: you really shouldn't use your home directory as your npm project directory. Do npm install in individual project directories. Yes, this wastes disk space but disk space is cheap and can freely be wasted. Even if you have 10 node.js projects you are unlikely to use more than 5GB of disk space even though there are lots of duplicate code files. A single HD movie is sometimes larger than that. Typical disk space usage for code is around 2GB.

sudo chown -R $USER /home/salman/node_modules
This command is useful.. Run it on your system..

Bcrypt refuses to install; no fixes have worked yet

This has been months worth of troubleshooting. I cannot npm install bcrypt no matter what I try.
I've tried sudo npm install bcrypt, brew install bcrypt, uninstalling node and reinstalling node, copying bcrypt files and editing my json files... Nothing works. Tested with alternatives to bcrypt, such as bcryptjs. This is only a problem with bcrypt packages, and I have tried dozens of suggestions and solutions I've found online to no avail.
Brew tells my bcrypt is installed, so I uninstall it through brew and it says it is still installed. I've done npm uninstall bcrypt -g just in case, but it still doesn't work. It says I don't have access to my node_modules folder, but, again, this only happens with bcrypt and literally nothing else. Express, postgresql, cors, body-parser, react, redux, thunk... Everything else installs and works without any issue.
npm WARN checkPermissions Missing write access to /Users/someUser/Desktop/realtorSite/server/node_modules
npm WARN server#1.0.0 No description
npm WARN server#1.0.0 No repository field.
npm ERR! path /Users/someUser/Desktop/realtorSite/server/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/Users/someUser/Desktop/realtorSite/server/node_modules'
npm ERR! [Error: EACCES: permission denied, access '/Users/someUser/Desktop/realtorSite/server/node_modules'] {
npm ERR! stack: 'Error: EACCES: permission denied, access ' +
npm ERR! "'/Users/someUser/Desktop/realtorSite/server/node_modules'",
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/Users/someUser/Desktop/realtorSite/server/node_modules'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/someUser/.npm/_logs/2019-06-16T22_38_43_256Z-debug.log
I just want to figure out what is wrong and be able to regularly use bcrypt and other encryption-based packages.

https://lightrains.com/blogs/fixing-npm-permissions-install-global
This link is how I fixed my issue. First, I used npm config get prefix to find my npm directory and cd ~ to get to my root directory. I then ran ls -a and found a node_modules folder in my root. By using ls -la node_modules, I found root was given all permissions by I had no rights. sudo chown -R someUser node_modules changed all permissions inside of node_modules to someUser instead of root.
Tested npm install bcrypt and it installs without issue.

create-react-app newproject commandline is not working for me

for some reason ive been ending up with "command not found" when i type in the create-react-app newproject command. Its been giving me this error:
npm WARN checkPermissions Missing write access to /Users/kennyquach/.npm-global/lib/node_modules/create-react-app
npm ERR! path /Users/kennyquach/.npm-global/lib/node_modules/create-react-app
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/Users/kennyquach/.npm-global/lib/node_modules/create-react-app'
npm ERR! { Error: EACCES: permission denied, access '/Users/kennyquach/.npm-global/lib/node_modules/create-react-app'
npm ERR! stack: 'Error: EACCES: permission denied, access \'/Users/kennyquach/.npm-global/lib/node_modules/create-react-app\'',
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/Users/kennyquach/.npm-global/lib/node_modules/create-react-app' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/kennyquach/.npm/_logs/2018-11-28T17_50_32_739Z-debug.log
any help is appreciated! Thanks!

As the error clearly shows you dont have write access to /Users/kennyquach/.npm-global/lib/node_modules/create-react-app
try changing access to 777 for all of .npm-global folders and then give a try.

You are high likely using Mac OS as Operating System. This is a general issue of globally installed packages in MacOS that caused by built-in node application's file permissions. Actually you can get over this by executing create-react-app as root, but i don't recommend that, it's not useful and it's risky.
So you got 2 options. (First one is hard to do, second is blazing fast)
1-) Completely remove Node from your System and install it with Brew. You can easily update node with that package manager and install any other popular developer tools too (Like: mongodb, mysql, pgsql, rabbitmq etc.).
You can get brew from here: https://brew.sh and install node with that code: brew install node
2-) You can easily give read, write, execute access to your folders and files. You can do it like this: sudo chmod -R 777 /Users/kennyquach/.npm-global/ when sudo asks your password, use your Administrator password.

This looks like an access issue. I faced same issue in MAC OS X, when I tried running the command with sudo, it worked for me.
sudo npm install -g create-react-app

npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules

Note: Due to security concerns, please don't use the marked solution but instead the highest voted one!
original question:
I am trying to install monaca with this command.
npm install -g monaca
But right after getting these errors:
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! path /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! { Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! stack: 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules\'',
npm ERR! errno: -13, npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/local/lib/node_modules' }
Any idea how to solve this problem?
Thank you

add following lines to ~/.bashrc after installing npm:
npm set prefix ~/.npm
PATH="$HOME/.npm/bin:$PATH"
PATH="./node_modules/.bin:$PATH"
Execute following line after changes:
source ~/.bashrc
and as mentioned by #contemplator avoid using sudo

This command will change the owner (chown) recursively (-R) for the current user in the specified directory
sudo chown -R $USER /usr/local/lib/node_modules

To all the warnings telling not to use sudo above, I'd add the following solution that worked pretty well for me while installing n, node version manager
sudo chown -R $USER /usr/local/lib/node_modules
This was taken from here: https://poopcode.com/missing-write-access-to-usr-local-lib-node-modules/
PS: for my specific use-case I also needed to run this one afterwards
sudo chown -R $USER /usr/local/bin/

Well, I used --save-dev and installed it not globally or using -g, the main problem occurs while you want it to write on default node_modules folder.
It solved my problem after 4 hours of checking multiple issues.
I even suggest you to use the npm init and make a package.json for a better dependency checking and then run npm install afterward. this video helps you for this https://www.youtube.com/watch?v=rTsz09zRuTU

Please dont use sudo.
I don't know the context of your environment, but I got the error on a server where Plesk was running.
Maybe the following command will help (via SSH) to check the permissions:
plesk repair fs example.com.
Manual: https://docs.plesk.com/en-US/12.5/administrator-guide/plesk-administration/plesk-repair-utility/plesk-repair-utility-file-system.74668/
In my case the node_modules folder was copied via FTP and therefore it had the wrong corrections. If necessary, you can remove this and install it via Plesk using the Npm installation button.
Info: The button only appears if the document contains a package.json with information.

it is very simple
you can use
sudo npm install -g kazam
or
su -
then
npm install -g kazam
explenation
su -
makes you as root ,who have permission to read , write and delete in all users
click here for the screen shot showing the error and the solution in the update of npm
this is for ubuntu i don't know is it work for other os

An inadvisable way to fix the issue would be to use sudo:
sudo npm install -g monaca
However it would be better to find a way around this without using sudo.
npm install -g less does not work