Fixes initial, clean build in projects using this loader

[Idorobots]

Because of how Webpack works, files created while typed-css-modules-loader executes aren't immediately visible to ts-loader what usually ends with a 'missing module' error the first time a project is built.
The standard solution is just to rerun the build, but that's not really suitable for CI in larger projects, so here's my proposed solution - it just creates a dummy file withing Webpacks memory FS along the actual one, so Webpack can forward its filename to ts-loader and then to tsc which, in turn, will access the actual file on the OS FS. 😃

Here's a seed project, where I'm using a similar hack. I've also tested the same project with a patched local version of typed-css-modules-loader and it seems to work fine.

[mohsen1]

@Idorobots Are you sure this is working? I could not make it work on my setup.

[Idorobots]

@mohsen1 I've tested it on a fresh clone of the seed project and you are totally right, it still reports an error during build:

(4,25): error TS2307: Cannot find module './navbar.css'.

However, the build continues, tests pass and the built app starts, so I must've missed it when I was testing it for this PR. I'll close it for now and see if I can find an actual fix. Thanks for pointing this out.

[mohsen1]

Thanks for letting me know. I'll dig into this soon. It shouldn't be impossible to tell Webpack those files exist.

[muuki88]

Hi folks. Has anyone made any progress on this? I haven't found anything on how
to tell webpack dependencies between loaders.