Since NPM and cnpm have been used together before, there is no problem. Today, when starting the Vue project, I encountered an error “NPM” ERR! code “Elifecycle” was initially used with NPM Run started and later changed to cnpm Neither can run. 
After checking the information, it is mostly said on the Internet that it is because of node_ There is a problem with the installation of modules. The basic solution is to clear the cache and reinstall.
The following steps are summarized:
1、npm cache clean — force
2、rm – rf node_ modules
3、rm – rf Package-lock.json (optional)
4、npm install
Read More:
- Solution of NPM err! Code elifecycle
- Error code elifecycle errorno when NPM install command is executed in Vue project
- The solution of NPM err! Code elifecycle
- NPM err! Code enotfound (2020-07-03)
- Solve NPM err! code 128
- NPM run serve reported an error “NPM err! Missing script: start”
- NPM run dev error (ERR: Code lifecycle)
- NPM err! Invalid name: “{{name}} in nuxt installation in p166 of Shangsi Valley online education project“
- When starting Vue project: cannot find module ‘webpack cli/bin/config yargs’ error [How to Fix]
- npm ERR! Error: CERT_ Untrusted problem solving
- gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildPr
- npm ERR Error: EPERM:operation not permitted, rename
- Vue project startup error: cannot find module XXX
- “NPM err! Error: eperm: operation not permitted” problem solving
- NPM install error | gyp err! Configure error
- Pull code execution NPM install error code: 128
- NPM ERR! Error: EACCES: permission denied, access ‘/usr/local/lib/node_modules’
- 【ipfs-api】npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.
- NPM install error: gyp err! Configure error
- NPM run build failed to package err! Missing script: build