Expected Behaviour
tsLoaderDefinitionFileVersions should be deterministic and output always the same source.
Actual Behaviour
tsLoaderDefinitionFileVersions is changing between builds (without any source code change), producing that webpack's hashing to get invalidated.
Steps to Reproduce the Problem
Please see discussion on webpack issue and findings: webpack/webpack#8419 (comment)
Location of a Minimal Repository that Demonstrates the Issue.
https://github.com/artola/webpack-bug
Running a few times the same build it will produce different file hashes due changes in tsLoaderDefinitionFileVersions.
The repo contains a demo with 2 files (foo.ts and bar.ts) and what I can see is that they are "sometimes" processed in different order ("foo then bar" most of times, until happens "bar then foo") producing the mentioned problem.
Expected Behaviour
tsLoaderDefinitionFileVersions should be deterministic and output always the same source.
Actual Behaviour
tsLoaderDefinitionFileVersions is changing between builds (without any source code change), producing that webpack's hashing to get invalidated.
Steps to Reproduce the Problem
Please see discussion on webpack issue and findings: webpack/webpack#8419 (comment)
Location of a Minimal Repository that Demonstrates the Issue.
https://github.com/artola/webpack-bug
Running a few times the same build it will produce different file hashes due changes in
tsLoaderDefinitionFileVersions.The repo contains a demo with 2 files (foo.ts and bar.ts) and what I can see is that they are "sometimes" processed in different order ("foo then bar" most of times, until happens "bar then foo") producing the mentioned problem.