Angular-cli doesn't watch for ALL files correctly.

[montella1507]

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.4.2
node: 7.5.0
os: win32 x64
@angular/common: 4.4.4
@angular/compiler: 4.4.4
@angular/core: 4.4.4
@angular/forms: 4.4.4
@angular/http: 4.4.4
@angular/platform-browser: 4.4.4
@angular/platform-browser-dynamic: 4.4.4
@angular/router: 4.4.4
@angular/cli: 1.4.2
@angular/compiler-cli: 4.4.4
typescript: 2.2.2

Repro steps.

watch bug.zip

1. npm install
2. ng serve
3. change anything in src/app/store/application-state.ts (it is linked in component, which is used in app.module.ts) and SAVE = NO REBUILD
4. Change (example) from storeData: string; to storeData: boolean; and RE-SAVE anything else where the watch is correctly watching = application successfully built, but it SHOULD NOT, because there is assignment:
   store.subscribe(x=> x.storeData = "pepa") but type of storeData has been changed to boolean...

Desired functionality.

It should watch for all files correctly

Mention any other details that might be useful.

• I have tried to change typescript to 2.4.0+ (because of breaking change in CHANGELOG) = NOT WORKING

• i have tried to update globally angular-cli(1.4.5) and create new APP via ng new = with latest dependencies = NOT WORKING

BTW even with latest Angular-cli, typescript version in dev-dependencies is "~2.3.3" despite your required version in CHANGELOG

[montella1507]

watch-bug-latest-cli.zip

Here is the SAME application, but generated with latest Angular-cli (1.4.5 -> ng new blabla), the same problem.. Application data is not being watched.

[montella1507]

Might be related to:
TypeStrong/ts-loader#156 but it was fixed months ago..

And:
TypeStrong/fork-ts-checker-webpack-plugin#36

But i have found this:
#5404 (comment)

so it may be actually a problem.

[hansl]

Closing this as duplicate of #7963

[montella1507]

@hansl what? this is definitely not truth! my problem is connected to:
TypeStrong/fork-ts-checker-webpack-plugin#36
and strongly connected to interfaces...

#7963

is different.

[hansl]

After investigating, you're correct in your assumption that it's not the same issue.

The problem is 3 fold:

1. TypeScript discards type information, and since you're only importing types that file will be discarded from the compilation output;
2. Since it's discarded from the output, Webpack does not know about the dependency between your file and the TypeScript that includes the type.
3. We rely on Webpack's dependency graph to actually know if something needs rebuilding.

The only point where we actually have control is point 3 and we should look at dependencies inside TypeScript and tell webpack about TS's dependency graph. I'll come up with a fix soon.