Re-bundle JS in a fresh environment #2710
Merged
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.
npm
/yarn
is non-deterministic when it comes to bundling dependencies, and so you can very easily end up with a dependency drift (especially when you're being strict about what you build elsewhere).It turns out that this is what #2680 was showing. If we clean the whole environment (
git clean -fdx
), then runsetup
and the other steps that the Action runs through, we get the same result.