core(legacy-javascript): update caniuse data #16699
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
connorjclark
requested review from
paulirish
and removed request for
a team
This reverts commit 9eb89c0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since updating to Node 22 this was crashing in CI (but never locally). I thought updating the data could resolve it, but it didn't. Then I thought updating browserify might, but it didn't. Then I found that disabling v8's compile cache could be a workaround, and it was.
Not sure how the compile cache is a problem now.
core/scripts/legacy-javascript/run.jsdoesn't do worker threads, and every file it bundles is done in a separate node process, so I would assume it wouldn't share any cache. shrug.