Update eslint globals, @cesium/eslint-config#13172
Merged
Conversation
|
Thank you for the pull request, @ggetz! ✅ We can confirm we have a CLA on file for you. |
Contributor
Author
|
@jjspace Could you please review? |
jjspace
approved these changes
Jan 30, 2026
jjspace
approved these changes
Jan 30, 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.
Description
Updated
globalseslint package, as well as the upstream compatibility updates in@cesium/eslint-config.Fixed a warning by removing an unneeded comment in
index.cjs— All.cjsfiles were already configured to use thenodeeslint configuration.Issue number and link
N/A; Part of routine release updates.
Testing plan
Ensure linting does not raise any errors or warnings. This is also run as part of CI.
Author checklist
CONTRIBUTORS.mdI have updatedCHANGES.mdwith a short summary of my changeI have added or updated unit tests to ensure consistent code coverageI have updated the inline documentation, and included code examples where relevant