Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-deprecate.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-dedupe.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-config.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-completion.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-ci.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-cache.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-bugs.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-bin.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-audit.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-adduser.md exists in filesystem Npm: /usr/lib/node_modules/npm/docs/content/commands/npm-access.md exists in filesystem Maybe it should be conflict with node/npm packages? or provide them? because otherwise when something is trying to install node/npm as dep: error: failed to commit transaction (conflicting files) I hope this issue will be solved, however, I have no idea why it happens in the first place. Sudo mv /usr/lib/node_modules.bak/* /usr/lib/node_modules # Move previously globally installed NPM packages into newly installed global `node_modules` # Remove packages installed by `npm` system package I worked this issue around simply renaming /usr/lib/node_modules, installing npm and restoring globally installed NPM packages: # Move old global `node_modules` Npm: /usr/lib/node_modules/npm/lib/utils/format-search-stream.js exists in filesystemĮrrors occurred, no packages were upgraded. Npm: /usr/lib/node_modules/npm/lib/package-url-cmd.js exists in filesystem The error from pacman -S npm (run via yay -S npm) I had today was: error: failed to commit transaction (conflicting files) I experienced same conflict as has described in his comment, at least twice in the past month (I think it occurred every time npm package installed via pacman was updated).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |