-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Closed
Labels
area: @angular-devkit/build-angulardevkit/build-angular:browserfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fix
Description
Command
build
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Touching the project index.html
file does not rebuild the application when using ng build --watch
.
It does rebuild when using ng serve
.
Using ng build -c development --watch
doesn't make a difference.
Minimal Reproduction
Create new workspace with ng new someapp
, choose default settings.
Run cd someapp && ng build --watch
and wait for build to finish.
In a separate terminal run touch src/index.html
. Observe no rebuild is happening.
Whereas touching index.html
when using ng serve
does cause a rebuild.
Exception or Error
No response
Your Environment
Angular CLI: 14.2.1
Node: 16.16.0
Package Manager: npm 8.11.0
OS: linux x64
Angular: 14.2.0
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router, upgrade
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1402.1
@angular-devkit/build-angular 14.2.1
@angular-devkit/core 14.2.1 (cli-only)
@angular-devkit/schematics 14.2.1
@angular/cli 14.2.1
@schematics/angular 14.2.1
rxjs 7.5.6
typescript 4.7.4
Anything else relevant?
No response
Metadata
Metadata
Assignees
Labels
area: @angular-devkit/build-angulardevkit/build-angular:browserfreq1: lowOnly reported by a handful of users who observe it rarelyOnly reported by a handful of users who observe it rarelyseverity3: brokentype: bug/fix