E2e tests use latest versions of contemporaneous libs and minor changes seem to yield unstable fingerprints on .css files.
This change redacts the fingerprints and allows, in most cases, webpack 4 and 5 to share the same source-map snapshots.
Some hackery was required to retrieve the name of the emitted .css file from the output directory given it is not easily available in env() or really anywhere outside assert().
Also commented the tests that no longer correctly reproduce the orphan-CR problem. I have tried to induce this problem a number of ways and have given up for now.
E2e tests use latest versions of contemporaneous libs and minor changes seem to yield unstable fingerprints on
.cssfiles.This change redacts the fingerprints and allows, in most cases, webpack 4 and 5 to share the same source-map snapshots.
Some hackery was required to retrieve the name of the emitted
.cssfile from the output directory given it is not easily available inenv()or really anywhere outsideassert().Also commented the tests that no longer correctly reproduce the orphan-CR problem. I have tried to induce this problem a number of ways and have given up for now.