-
Notifications
You must be signed in to change notification settings - Fork 12k
Watching doesn't work for file paths remapped by the provided FS host #11339
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
Comments
I looked a bit into this today. The current behaviour is due to us using Webpack's watcher to watch files in angular-cli/packages/ngtools/webpack/src/virtual_file_system_decorator.ts Lines 107 to 142 in 6449a75
Instead, we should be using our own watcher implementation, that uses I am unsure how much work this is since there might not be a one-to-one correspondence in functionality between the webpack watcher and the host watch functionality. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Area
Versions
node v9.5.0
npm 5.7.1
Linux Fedora 25
Repro steps
Create a new ng cli project. Build it in production mode. As specified by the
angular.json
file, the requests to theenvironment.ts
file are remapped toenvironment.prod.ts
. However, if you change theenvironment.prod.ts
file, that webpack won't rebuild the project. Also, if you change the originally requested file -environment.ts
, webpack will detect the change and trigger a build.Desired functionality
The app should be rebuild when a remapped file is changed.
Mention any other details that might be useful
It looks like the original paths (and not the remapped ones) are added as dependencies for the webpack compilation in the
@ngtools/webpack
loader - here. The same thing happens for the original component templates and styles (html, css, scss files).The text was updated successfully, but these errors were encountered: