Watch doesn't work with @ngtools/webpack

[dawidgarus]

Versions

os: Windows 8.1
node: 6.13.0
npm: 3.10.10

"@angular/common": "^5.2.1",
"@angular/compiler": "^5.2.1",
"@angular/compiler-cli": "^5.2.1",
"@angular/core": "^5.2.1",
"@angular/platform-browser": "^5.2.1",
"@angular/platform-browser-dynamic": "^5.2.1",
"@ngtools/webpack": "^1.10.0",
"raw-loader": "^0.5.1",
"rxjs": "^5.5.2",
"typescript": "^2.5.3",
"webpack": "^3.10.0"
"zone.js": "^0.8.18"

Repro steps

• clone repo: https://github.com/dawidgarus/ngtools-watch
• run npm install
• run node compile
• change any ts or html file other than main.ts or app.module.ts

Observed behavior

Despite the fact that file has changed, project is not recompiled.
But when main.ts or app.module.ts changes, then project is recompiled, so watcher seems to be working.

Desired behavior

Project should be recompiled after change.

Mention any other details that might be useful (optional)

EDIT:
It seems to be working fine without skipCodeGeneration: true - it might be issue with that.

[dawidgarus]

After further investigation, I found that the reason it didn't was extensions order in webpack config. Apparently, ts must come before js. I think it should be mentioned somewhere in the docs. Angular docs on webpack say that you need to specify extensions (https://angular.io/guide/webpack#resolve-extension-less-imports) and provides example, but it fails to mention the significance of the order.

[jtomaszewski]

Yes, it should be mentioned, I agree. It took me 3 hours to find the issue. Related: #8508

[alan-agius4]

Closing as docs have been fixed.

[angular-automatic-lock-bot]

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.}