Background
After NVM use switches the node version, NPM reports an error segmentation fault
My solution
sudo apt autoremove npm
Note: it must be autoremove, not remove. Remove is not completely cleared
Cause guess
There is a global NPM. The configuration of the global NPM affects the configuration of the NPM version corresponding to the node installed by the NVM
Read More:
- [Solved] node exporter service startup error: segmentation fault
- How to Solve NPM Error: listen EADDRINUSE 127.0.0.1:8080
- How to Solve NPM Error 426 Upgrade Required
- npm ERR! Failed at the [email protected] install script.
- [Solved] npm install Error: Error: EACCES: permission denied
- Using apt get to delete software completely
- [Solved] Linux program error: dpkg is interrupted. You must manually run ‘sudo dpkg — configure – a’
- Kali starts SSH service error [How to Fix]
- [Solved] docker: Error response from daemon: OCI runtime create failed: container_linux.go:380
- [Solved] ubuntu Boot Error: /dev/nume0n1p2:clean
- Ubuntu Error: dpkg: error processing package mysql-community-server (–configure):
- Linux apt-get update Error: Error in `appstreamcli‘: double free or corruption … Aborted (core dumped)
- How to Fix Linux sub process /usr/bin/dpkg returned an error code (1)
- [Solved] Linux error E: dpkg is broken, you must manually run ‘sudo dpkg –configure -a’ to resolve this issue
- [Solved] Ubuntu 20.04 Error: curl: (23) Failure writing output to destination
- [Solved] dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
- [Solved] gawk: error while loading shared libraries: libreadline.so.4
- Linux Virtual Machine Boot Container: Error response from daemon: driver failed programming external connectivity on endpoint
- [Solved] Ubuntu18.04 Px4 (xtdrone) gazebo joint simulate error