-
-
Notifications
You must be signed in to change notification settings - Fork 433
Interface change doesn't trigger change in webpack #156
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 am experiencing the same issue as well (interface changes not triggering webpack) with a different starter kit: |
@chadaustin reported an issue via twitter that I believe is related: https://twitter.com/chadaustin/status/705542582189715456 Sorry for the delay on this. I'm planning on taking a look this weekend. |
I think I may be experiencing this too but I'm not sure. Certainly I'm breaking things, fixing them and then having to re-kick off my watcher. No great hardship but it would be nice if I didn't have to do that every now and then. |
There's a test for this kind of thing at https://github.com/TypeStrong/ts-loader/tree/master/test/typeSystemWatch but there must be some case that is being missed. |
Interesting, I see the same thing. Often the loader will stop seeing On 4 March 2016 at 15:08, James Brantly notifications@github.com wrote:
|
I've tried https://www.npmjs.com/package/awesome-typescript-loader and it handles this case perfectly |
Released in v0.8.2 |
For example:
->
In this case, it does not trigger update process.
The main question is why it does not trigger an update when I made changes only in interfaces?
Thanks.
The text was updated successfully, but these errors were encountered: