Remove file fingerprints from e2e assertions #220
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.