Skip to content

Fix the lint errors @eslint/js 10's recommended rules raise - #168

Merged
jgfoster merged 1 commit into
mainfrom
mfernandez/eslint10-fixes
Oct 21, 2026
Merged

jgfoster merged 1 commit into
mainfrom
mfernandez/eslint10-fixes

Conversation

@MatiasFernandez

Copy link
Copy Markdown
Collaborator

This is needed before the Dependabot bump in #156 can go in. That PR fails lint because @eslint/js 10 adds two rules to recommended:

  • preserve-caught-error: in config.ts and engine.ts, a catch that throws a new Error now passes the original error as { cause: e }, so its stack trace isn't lost.
  • no-useless-assignment: in savedObjects.ts and debugConsole.test.ts, I removed an initial value that every path overwrites.

There's no change in behaviour. I checked locally that eslint . passes with both @eslint/js 9 and 10. Once this merges, rebase #156 (@dependabot rebase).

🤖 Generated with Claude Code

@eslint/js 10 adds preserve-caught-error and no-useless-assignment to
its recommended set. Attach the caught error as `cause` where a catch
rethrows a new Error, and drop two initialisers every path overwrites.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MatiasFernandez
MatiasFernandez marked this pull request as ready for review October 20, 2026 21:47
@jgfoster
jgfoster added this pull request to the merge queue Oct 21, 2026
Merged via the queue into main with commit f1402b3 Oct 21, 2026
5 checks passed
@jgfoster
jgfoster deleted the mfernandez/eslint10-fixes branch October 21, 2026 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants