Skip to content

chore(deps-dev): bump eslint from 9.39.2 to 10.1.0 in /frontend#206

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/frontend/eslint-10.1.0
Open

chore(deps-dev): bump eslint from 9.39.2 to 10.1.0 in /frontend#206
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/frontend/eslint-10.1.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 1, 2026

Bumps eslint from 9.39.2 to 10.1.0.

Release notes

Sourced from eslint's releases.

v10.1.0

Features

  • ff4382b feat: apply fix for no-var in TSModuleBlock (#20638) (Tanuj Kanti)
  • 0916995 feat: Implement api support for bulk-suppressions (#20565) (Blake Sager)

Bug Fixes

  • 2b8824e fix: Prevent no-var autofix when a variable is used before declaration (#20464) (Amaresh S M)
  • e58b4bf fix: update eslint (#20597) (renovate[bot])

Documentation

  • b7b57fe docs: use correct JSDoc link in require-jsdoc.md (#20641) (mkemna-clb)
  • 58e4cfc docs: add deprecation notice partial (#20639) (Milos Djermanovic)
  • 7143dbf docs: update v9 migration guide for @eslint/js usage (#20540) (fnx)
  • 035fc4f docs: note that globalReturn applies only with sourceType: "script" (#20630) (Milos Djermanovic)
  • e972c88 docs: merge ESLint option descriptions into type definitions (#20608) (Francesco Trotta)
  • 7f10d84 docs: Update README (GitHub Actions Bot)
  • aeed007 docs: open playground link in new tab (#20602) (Tanuj Kanti)
  • a0d1a37 docs: Add AI Usage Policy (#20510) (Nicholas C. Zakas)

Chores

  • a9f9cce chore: update dependency eslint-plugin-unicorn to ^63.0.0 (#20584) (Milos Djermanovic)
  • 1f42bd7 chore: update prettier to 3.8.1 (#20651) (루밀LuMir)
  • c0a6f4a chore: update dependency @​eslint/json to ^1.2.0 (#20652) (renovate[bot])
  • cc43f79 chore: update dependency c8 to v11 (#20650) (renovate[bot])
  • 2ce4635 chore: update dependency @​eslint/json to v1 (#20649) (renovate[bot])
  • f0406ee chore: update dependency markdownlint-cli2 to ^0.21.0 (#20646) (renovate[bot])
  • dbb4c95 chore: remove trunk (#20478) (sethamus)
  • c672a2a test: fix CLI test for empty output file (#20640) (kuldeep kumar)
  • c7ada24 ci: bump pnpm/action-setup from 4.3.0 to 4.4.0 (#20636) (dependabot[bot])
  • 07c4b8b test: fix RuleTester test without test runners (#20631) (Francesco Trotta)
  • 079bba7 test: Add tests for isValidWithUnicodeFlag (#20601) (Manish chaudhary)
  • 5885ae6 ci: unpin Node.js 25.x in CI (#20615) (Copilot)
  • f65e5d3 chore: update pnpm/action-setup digest to b906aff (#20610) (renovate[bot])

v10.0.3

Bug Fixes

  • e511b58 fix: update eslint (#20595) (renovate[bot])
  • f4c9cf9 fix: include variable name in no-useless-assignment message (#20581) (sethamus)
  • ee9ff31 fix: update dependency minimatch to ^10.2.4 (#20562) (Milos Djermanovic)

Documentation

  • 9fc31b0 docs: Update README (GitHub Actions Bot)
  • 4efaa36 docs: add info box for eslint-plugin-eslint-comments (#20570) (DesselBane)
  • 23b2759 docs: add v10 migration guide link to Use docs index (#20577) (Pixel998)
  • 80259a9 docs: Remove deprecated eslintrc documentation files (#20472) (Copilot)
  • 9b9b4ba docs: fix typo in no-await-in-loop documentation (#20575) (Pixel998)
  • e7d72a7 docs: document TypeScript 5.3 minimum supported version (#20547) (sethamus)

Chores

  • ef8fb92 chore: package.json update for eslint-config-eslint release (Jenkins)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Greptile Summary

This PR is a Dependabot-generated major version upgrade of eslint from 9.39.2 to 10.1.0 in the frontend. ESLint v10 removes legacy .eslintrc support, bumps several internal packages to new majors (eslint-scope v9, espree v11, eslint-visitor-keys v5, minimatch v10), and raises the Node.js minimum to ^20.19.0 || ^22.13.0 || >=24.

Key findings:

  • Incomplete bump — @eslint/js left at ^9.32.0: @eslint/js is a companion package to eslint versioned in lockstep. eslint.config.js imports it directly (import js from \"@eslint/js\") and uses js.configs.recommended. Leaving it on v9 while eslint runs v10 is an unsupported combination that could silently produce incorrect lint results or break the lint run outright. This package should also be bumped to ^10.1.0.
  • Node.js 18 dropped: ESLint v10 no longer supports Node.js 18 or Node.js 20 < 20.19.0. CI environments or developer machines on those versions will fail when running npm run lint.
  • The removal of @eslint/eslintrc from the transitive dependency tree is expected since the project already uses flat config (eslint.config.js), so that specific breaking change does not affect this repo.

Confidence Score: 3/5

Not safe to merge as-is — @eslint/js must be co-bumped to v10 to match eslint@10.x before this upgrade is complete.

There is a clear P1 defect: @eslint/js is left at ^9.32.0 while eslint moves to ^10.1.0. The flat config in eslint.config.js imports @eslint/js directly and uses js.configs.recommended, so this version mismatch will either break linting or produce undefined behaviour. The PR is genuinely incomplete.

frontend/package.json@eslint/js version must be bumped to ^10.1.0 alongside eslint.

Important Files Changed

Filename Overview
frontend/package.json Bumps eslint from ^9.32.0 to ^10.1.0, but fails to bump the companion package @eslint/js from ^9.32.0 — a version mismatch that can break the flat config setup.
frontend/package-lock.json Lockfile updated to reflect ESLint 10.1.0 and its transitive dependency changes: removes @eslint/eslintrc, chalk, lodash.merge, js-yaml, import-fresh and bumps eslint-scope, eslint-visitor-keys, espree, acorn, and minimatch to new major versions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["eslint@10.1.0\n(bumped ✅)"] -->|"requires"| B["@eslint/js@10.x\n(NOT bumped ❌ still at ^9.32.0)"]
    A -->|"requires"| C["eslint-scope@9.1.2"]
    A -->|"requires"| D["eslint-visitor-keys@5.0.1"]
    A -->|"requires"| E["espree@11.2.0"]
    A -->|"requires"| F["minimatch@10.2.5"]
    A -->|"removed"| G["@eslint/eslintrc\n(legacy .eslintrc support dropped)"]
    A -->|"removed"| H["chalk / lodash.merge / js-yaml"]
    B -->|"used in"| I["eslint.config.js\nimport js from '@eslint/js'\njs.configs.recommended"]
    style B fill:#f96,stroke:#c00
    style G fill:#ccc,stroke:#999
    style H fill:#ccc,stroke:#999
Loading

Comments Outside Diff (1)

  1. frontend/package.json, line 78 (link)

    P1 @eslint/js not bumped to match ESLint v10

    @eslint/js is still pinned to "^9.32.0" while eslint has been bumped to "^10.1.0". These two packages are developed and versioned in sync within the same monorepo — @eslint/js@9.x is designed to accompany eslint@9.x.

    eslint.config.js directly imports this package:

    import js from "@eslint/js";
    // ...
    extends: [js.configs.recommended, ...tseslint.configs.recommended],

    Running eslint@10.x with @eslint/js@9.x is an untested and unsupported combination. Rule definitions, config structures, or internal types that @eslint/js exports may differ between major versions, potentially causing linting failures or silently incorrect rule application.

    This PR should also bump @eslint/js to ^10.1.0:

    Prompt To Fix With AI
    This is a comment left during a code review.
    Path: frontend/package.json
    Line: 78
    
    Comment:
    **`@eslint/js` not bumped to match ESLint v10**
    
    `@eslint/js` is still pinned to `"^9.32.0"` while `eslint` has been bumped to `"^10.1.0"`. These two packages are developed and versioned in sync within the same monorepo — `@eslint/js@9.x` is designed to accompany `eslint@9.x`.
    
    `eslint.config.js` directly imports this package:
    ```js
    import js from "@eslint/js";
    // ...
    extends: [js.configs.recommended, ...tseslint.configs.recommended],
    ```
    
    Running `eslint@10.x` with `@eslint/js@9.x` is an untested and unsupported combination. Rule definitions, config structures, or internal types that `@eslint/js` exports may differ between major versions, potentially causing linting failures or silently incorrect rule application.
    
    This PR should also bump `@eslint/js` to `^10.1.0`:
    
    
    How can I resolve this? If you propose a fix, please make it concise.
Prompt To Fix All With AI
This is a comment left during a code review.
Path: frontend/package.json
Line: 78

Comment:
**`@eslint/js` not bumped to match ESLint v10**

`@eslint/js` is still pinned to `"^9.32.0"` while `eslint` has been bumped to `"^10.1.0"`. These two packages are developed and versioned in sync within the same monorepo — `@eslint/js@9.x` is designed to accompany `eslint@9.x`.

`eslint.config.js` directly imports this package:
```js
import js from "@eslint/js";
// ...
extends: [js.configs.recommended, ...tseslint.configs.recommended],
```

Running `eslint@10.x` with `@eslint/js@9.x` is an untested and unsupported combination. Rule definitions, config structures, or internal types that `@eslint/js` exports may differ between major versions, potentially causing linting failures or silently incorrect rule application.

This PR should also bump `@eslint/js` to `^10.1.0`:
```suggestion
    "@eslint/js": "^10.1.0",
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: frontend/package-lock.json
Line: 5430-5432

Comment:
**ESLint v10 raises the Node.js minimum version**

The new engine requirement for `eslint@10.x` is `^20.19.0 || ^22.13.0 || >=24`, dropping support for Node.js 18 entirely and requiring Node.js 20.19.0+ (not just any Node 20). If any CI runner, Docker image, or developer machine is on Node.js 18 or Node.js 20 < 20.19.0, the `lint` script will break.

It's worth verifying the Node.js version in `.nvmrc`, `.node-version`, CI workflow files, or `engines` field in `package.json` is compatible with this new requirement before merging.

How can I resolve this? If you propose a fix, please make it concise.

Reviews (1): Last reviewed commit: "chore(deps-dev): bump eslint from 9.39.2..." | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.

Bumps [eslint](https://github.com/eslint/eslint) from 9.39.2 to 10.1.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v9.39.2...v10.1.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-version: 10.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Comment on lines 5430 to 5432
"eslint": "bin/eslint.js"
},
"engines": {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 ESLint v10 raises the Node.js minimum version

The new engine requirement for eslint@10.x is ^20.19.0 || ^22.13.0 || >=24, dropping support for Node.js 18 entirely and requiring Node.js 20.19.0+ (not just any Node 20). If any CI runner, Docker image, or developer machine is on Node.js 18 or Node.js 20 < 20.19.0, the lint script will break.

It's worth verifying the Node.js version in .nvmrc, .node-version, CI workflow files, or engines field in package.json is compatible with this new requirement before merging.

Prompt To Fix With AI
This is a comment left during a code review.
Path: frontend/package-lock.json
Line: 5430-5432

Comment:
**ESLint v10 raises the Node.js minimum version**

The new engine requirement for `eslint@10.x` is `^20.19.0 || ^22.13.0 || >=24`, dropping support for Node.js 18 entirely and requiring Node.js 20.19.0+ (not just any Node 20). If any CI runner, Docker image, or developer machine is on Node.js 18 or Node.js 20 < 20.19.0, the `lint` script will break.

It's worth verifying the Node.js version in `.nvmrc`, `.node-version`, CI workflow files, or `engines` field in `package.json` is compatible with this new requirement before merging.

How can I resolve this? If you propose a fix, please make it concise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:frontend React frontend dependencies Dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant