Conversation
maribethb
approved these changes
Mar 2, 2026
Contributor
|
I wonder if it has to do with the node versions supported by the older package. the previous version in package.json claims it works with node ">=18" so there's no upper bound set, but perhaps something else under the hood caused it to not be compatible. that's the only relevant difference I can think of with v13. hopefully this fixes it Once And For All (TM) |
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
2 participants
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.
The basics
The details
Resolves
This PR updates the version of the Closure compiler in use on the v13 branch to the latest, hopefully fixing CI.