-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Update closure-compiler to 20251216.0.0 #26015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Update closure-compiler to 20251216.0.0 #26015
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR updates the google-closure-compiler dependency from version 20240317.0.0 to 20251216.0.0 and removes duplicate extern definitions that are now provided natively by the newer Closure Compiler version.
- Updates google-closure-compiler to version 20251216.0.0
- Removes duplicate externs for Atomics.waitAsync and WebAssembly.Global
- Updates transitive dependencies including vinyl (2.2.1 → 3.0.1) and replace-ext (1.0.1 → 2.0.0)
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/closure-externs/closure-externs.js | Removes duplicate extern definitions for Atomics.waitAsync and WebAssembly.Global that are now provided by the updated Closure Compiler |
| package.json | Updates google-closure-compiler version from 20240317.0.0 to 20251216.0.0 |
| package-lock.json | Updates google-closure-compiler and its dependencies, including new platform-specific binaries (linux-arm64, macos) and updated transitive dependencies (vinyl 3.0.1, replace-ext 2.0.0, and new dependencies like streamx, teex, b4a) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sbc100
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I seem to remember that I didn't land #24679 because it contained some code size regressions that we wanted addressed before we landed it.
Are the regressions in this change less serious than in #24679?
Is there any particular reason you want this upgrade? i.e. is there some feature of closure compiler you want?
| /** | ||
| * @param {number=} maxWaitMilliseconds | ||
| */ | ||
| /** @suppress {duplicate, checkTypes} */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge this with the existing docstring above.
| return True | ||
| if arg == '--externs' and i + 1 < len(args) and 'webgpu-externs.js' in args[i + 1]: | ||
| return True | ||
| return False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just keep this simple and do return any('webgpu-externs.js' in a for a in args).
Does it matter if webgpu-externs-fixes.js is included even when its not strictly needed?
I assume webgpu-externs.js is part of the emdawn project? If so we should probably file a bug there to get it fixed and leave commend here to remove this code once its fixed.
Supersedes #24679.
Context
Changes
Tests
Notes