Due to domestic and foreign environmental factors, NPM install often has various problems, especially “error: eperm: operation not permitted, unlink…” This is a mistake.
This error is misleading because of the error information, which leads to a lot of solutions proposed on the Internet, such as setting permissions and entering as an administrator.
In fact, the reason for this error is that the network is unstable, resulting in incomplete or error downloading of NPM package. What, your home’s 100m optical fiber network is flying fast?But the server is foreign, so it should be slow when it is slow.
After an error, most people will NPM install again, and the NPM install command will not take the initiative to clear the last installed package. However, the package you installed last time is incomplete, and there is a dependency relationship between packages. As a result, errors will naturally occur.
Therefore, in order to solve this problem, you should clear the last installed package. If you want to clear it completely, you generally need the following two steps:
Delete all files in node modules. Clear the NPM cache.
There are two ways to delete the node modules file:
1. Right click to delete it directly. The disadvantage is that the deletion speed is very slow when there are too many dependencies.
2. Install rimraf to delete [wall crack recommended, speed of light].
Install (Global install recommended)
npm install -g rimraf
first in node_ The folder where the modules are located. And then directly input:
rimraf node_ modules
There are two ways to clear the NPM cache:
the first one is to delete the cache file directly, and delete the file of C: (users \ \ user name. Npmrc).
The second is to execute: NPM cache clean — force, which also achieves the purpose of clearing cache files.
- Error: EPERM: operation not permitted, mkdir ‘D:\nodejs\node_modules\npm\node_cache\_npx‘
- npm ERR! Error: EPERM: operation not permitted, open ‘C:\Program Files\nodejs\node_ Solution to cache / xxx
- NPM install Error: EPERM: operation not permitted, mkdir solution
- npm ERR Error: EPERM:operation not permitted, rename
- “NPM err! Error: eperm: operation not permitted” problem solving
- [Vue] install vuex, error: eperm: operation not permitted, rename
- EPERM: operation not permitted, symlink ‘../../’
- java.net.SocketException: socket failed: EPERM (Operation not permitted)
- NPM can’t find D: //nodejs/node all of The solution of sudden_modules/NPM/bin/npm-cli.js
- AVD FFmpeg avcodec_ A solution of open2 returning – 1 (operation not permitted)
- PHP artisan cache: clear command reports an error
- On the use of NPM cache clean — force
- [Solved] gitbook: node_modules\npm\node_modules\graceful-fs\polyfills.js:287
- After adb is connected to an android phone, remount failed: operation not permitted when adb remount is a roundabout solution
- ADB remount failed: operation not permitted
- linux docker Error Failed to get D-Bus connection: Operation not permitted
- docker service Failed to get D-Bus connection: Operation not permitted
- Docker CentOS Failed to get D-Bus connection: Operation not permitted
- [Solved] This dependency was not found: * core-js/modules/es.error.cause.js in ./node_modules/@babel
- Tensorflow operation report error modulenotfounderror: no module named ‘tensorflow. Python. Types’ solution