Open jauniuse opened 6 years ago
Yes sir, me too. Building works fine, but problems arise when resolving modules at runtime.
A tiny repro would help but my guess is that it's because we use symbols on dependencies
and that cache loader serializes them to disk and back (and looses that information in the process).
If a repro confirms that changing the symbol to a string fixes this without unwanted effect we might consider the change.
I'm submitting a bug report
Please tell us about your environment:
Operating System: Windows 10
Node Version: 6.11.1
NPM Version: 3.10.10
JSPM OR Webpack AND Version webpack 4.4.1
Browser: all
Language: TypeScript 2.6
Current behavior:
I want to use cache-loader in order to speed up webpack builds. As soon as I try to use cache-loader with ts-loader, during runtime modules defined with
PLATFORM.ModuleName('XXX')
cannot be resolved resulting in errorUnable to find module with XXX
.Expected behavior: Modules defined with
PLATFORM.ModuleName('XXX')
should be resolved during runtime when using cache-loader and should not result in error.