fix(@ngtools/webpack): resolve file name before invalidating cached files

[msmorgan]

Fix WebpackCompilerHost cache invalidation behavior on Windows systems. Previously, invalidate made no call to _resolve, causing paths with backslashes not to match the file cache. This caused a watch build to continuously emit the same result.

Fixes #4422
Fixes #4345
Fixes #4338

[quanterion]

Thanks! This problem makes a lot of pain to me

[kwdiggs]

Good stuff!

[hansl]

LGTM. You're right, this was an oversight and we were missing e2e tests for this. I'll add a test. Thanks!

[msmorgan]

@hansl Btw, this caching has made watched builds so much faster. Thanks!

[rohitsodhia]

I'm kinda hoping it's just me, and just this project, but while this fix almost completely resolved #4422, I'm noticing sometimes when I make minor changes (I just changed a variable from 2500 to 2000), it still uses the old has and forces me to stop ng serve and restart. I'm not sure if I should have noted this here or in 4422, but thought this was better? It seems to work the vast majority of the time, but on some small changes (not even all), it still reuses a hash.

[quanterion]

@hansl Any plans to release a next beta? This issue is a showstopper for windows users((

[slubowsky]

@quanterion If you install latest webpack (1.2.8) problem is fixed. If you delete node_modules and redo npm install you'll get that version with current cli release as it pulls in latest (I think)

[msmorgan]

@rohitsodhia The behavior I've noticed is that sometimes after running for a long time the build freezes up and doesn't emit new files consistently, especially for small changes on a file I've been editing a lot recently.

Is this consistent with your experience?

[rohitsodhia]

@msmorgan I didn't notice any freezing... it always emitted, just not updating the hash. Following the upgrade path resolved the problems for me.

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