Skip to content

cannot find module 'abbrev' after installation of Angular CLI RC4 #5588

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mattalco opened this issue Mar 23, 2017 · 3 comments
Closed

cannot find module 'abbrev' after installation of Angular CLI RC4 #5588

mattalco opened this issue Mar 23, 2017 · 3 comments

Comments

@mattalco
Copy link

mattalco commented Mar 23, 2017

Bug Report or Feature Request (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.

image

Ubuntu 16.04

node -v
v6.10.1

npm -v
3.10.10

Repro steps.

run npm install -g @angular/cli@latest
run ng -v

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

@filipesilva
Copy link
Contributor

I think this is a dupe of an old issue: #1190. It seems to be a problem with npm.

@yabbes
Copy link

yabbes commented Jul 19, 2017

I also had this same problem what I did to fix it on Linux Mint:

  • change ownership of /usr/lib/node_modules to my user to stop executing npm with sudo as this is highly discouraged.
  • run npm uninstall -g @angular/cli and npm cache clean (--force)
  • check if ~/.npm was clean, else rm -rf ~/-npm
  • try reinstalling npm install -g @angular/cli
  • go to ...node_modules/angular-cli and run npm install
  • run npm install --save-dev @angular/cli@latest
  • and finally i can run ng -v with no error..

but this was quite a lot of trouble I faced lol, I'm posting this here so maybe it helps other people

**Edit: **
I think many of these problems could possibly be avoided when you configure your npm's default directory according to their installation instructions on the website.

https://docs.npmjs.com/getting-started/fixing-npm-permissions#option-2-change-npms-default-directory-to-another-directory

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants