Skip to content
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

Live reload failing with webpack 2.1.0-beta.22 , angular-cli: 1.0.0-beta.14 #2139

Closed
dessalines opened this issue Sep 15, 2016 · 8 comments
Closed

Comments

@dessalines
Copy link

I've noticed ng serve isn't picking up my file changes, and I have to rerun it every time I make a save.

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.14
node: 6.5.0
os: linux x64
@HamidHabib
Copy link

HamidHabib commented Sep 15, 2016

Try this:
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@webpack

@dessalines
Copy link
Author

Just did this, didn't fix the issue. Did changing a file work for you?

@HamidHabib
Copy link

I didnt change anything. i just run those commands and got everything up and running to (v2.0.0 latest Angular)
give this a try:
watchman from npm and watchman from brew are 2 different things

brew update
brew install watchman

@dessalines
Copy link
Author

I'm on linux. I mean, did you try changing a file to make sure its reloading webpack? I'm guessing the library is watchpack, mines on watchpack@^0.2.1.

I just tried this on two different computers BTW, and live-reload isn't working.

@jabaa
Copy link

jabaa commented Sep 17, 2016

I have the same problem on Xubuntu 16.04. I got the same error message and I installed watchman from source as described in https://ember-cli.com/user-guide/#watchman. The error message is gone but the live reload isn't triggered on file change.

@osechet
Copy link

osechet commented Sep 20, 2016

This issue looks similar to #1610.

@dessalines
Copy link
Author

I fixed this by removing running rm -rf node_modules , and reinstalling angular-cli both globally and locally.

@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 6, 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

4 participants