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

ng serve does not detect file changes in a folder watched by Dropbox #6823

Closed
gsdefender opened this issue Jun 28, 2017 · 2 comments
Closed
Assignees
Labels
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity2: inconvenient type: bug/fix

Comments

@gsdefender
Copy link

gsdefender commented Jun 28, 2017

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.1.3
node: 6.11.0
os: darwin x64
@angular/animations: 4.2.4
@angular/common: 4.2.4
@angular/compiler: 4.2.4
@angular/core: 4.2.4
@angular/forms: 4.2.4
@angular/http: 4.2.4
@angular/platform-browser: 4.2.4
@angular/platform-browser-dynamic: 4.2.4
@angular/router: 4.2.4
@angular/cli: 1.1.3
@angular/compiler-cli: 4.2.4
@angular/language-service: 4.2.4

Dropbox 29.4.20
O.S. OS X Yosemite

Repro steps.

Create a project inside a Dropbox controlled folder.
Run ng serve.
Modify a file inside the project directory. No change detected.

Do the same in a folder that is not under Dropbox control and it works.

The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

@filipesilva
Copy link
Contributor

This sounds like webpack/webpack#2258, which was moved to webpack/watchpack#42. Basically the parenthesis break serve.

@filipesilva filipesilva self-assigned this Jun 29, 2017
@filipesilva filipesilva added blocked P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity2: inconvenient type: bug/fix labels Jun 29, 2017
@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
P5 The team acknowledges the request but does not plan to address it, it remains open for discussion severity2: inconvenient type: bug/fix
Projects
None yet
Development

No branches or pull requests

2 participants