Open
Conversation
This was referenced Feb 26, 2026
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.
v10ES2022in browser recommended config, see Consider updating to ECMA version 2022 cesium#12623.prettierrc, fix changelog headingsThe migration guide is here: https://eslint.org/docs/latest/use/migrate-to-10.0.0
When doing this update the biggest change that affects us is the 3 new rules added to the base JS recommendataions from
@eslint/jsoutlined here.We may want to hold off merging this PR and publishing a new release until we've decided if any of these should be disabled again. This can be done easily by cloning both repos and updating the npm package version for the eslint config to
file://[path to this repo]