Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@antfu/eslint-config	7.2.0 → 7.4.3
@eslint-react/eslint-plugin (source)	2.7.2 → 2.13.0
@leanix/reporting	0.4.171 → 0.4.172
@types/node (source)	24.10.9 → 24.10.13
@vitejs/plugin-react (source)	5.1.2 → 5.1.4
eslint-plugin-react-refresh	0.4.26 → 0.5.0
npm (source)	11.9.0 → 11.10.0
rimraf	6.1.2 → 6.1.3
semver	7.7.3 → 7.7.4

---

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v7.4.3

Compare Source

   🐞 Bug Fixes

• Formating regression  -  by @​antfu (2ef8a)

    View changes on GitHub

v7.4.2

Compare Source

   🐞 Bug Fixes

• Relax eslint peer deps range  -  by @​antfu (b5f53)

    View changes on GitHub

v7.4.1

Compare Source

   🐞 Bug Fixes

• Ignore typescript files when typescript is off  -  by @​antfu (bda75)

    View changes on GitHub

v7.4.0

Compare Source

   🚀 Features

• Angular support  -  by @​St2r and @​antfu in #​804 (67b1b)

   🐞 Bug Fixes

• Update peer dependency requirement for eslint-plugin-react-refresh  -  by @​hyoban in #​813 (19a43)

    View changes on GitHub

v7.3.0

Compare Source

   🚀 Features

• Upgrade eslint-plugin-react-refresh, eslint-plugin-regexp  -  by @​antfu (610e7)
• react: Sync recommend rules  -  by @​hyoban in #​810 (1b870)

   🐞 Bug Fixes

• Use ConfigWithExtends instead of Linter.Config  -  by @​hyoban in #​809 (ad4e5)

    View changes on GitHub

Rel1cx/eslint-react (@​eslint-react/eslint-plugin)

v2.13.0

Compare Source

✨ New

• Add naming-convention/id-name rule for React.useId() by @​amir-rahmanii in #​1497
• Deprecate naming-convention/filename and naming-convention/filename-extension by @​Rel1cx in #​1498

🐞 Fixes

• Update rules’ meta.type from "problem" to "suggestion" for naming-convention rules by @​amir-rahmanii in #​1496

📝 Changes you should be aware of

1. The naming-convention/filename rule has been deprecated and will be removed in the next major version.
2. The naming-convention/filename-extension rule has been deprecated and will be removed in the next major version.

Modern React frameworks each come with their own naming conventions that can differ or even conflict. A single predefined, framework-agnostic filename or filename extension rule no longer matches real-world usage. Please follow the official naming conventions of the specific React framework you are using.

For example, here are some references for popular frameworks:

• Next.js — App Router and File-system conventions: https://nextjs.org/docs/app, https://nextjs.org/docs/app/api-reference/file-conventions
• React Router — File Route Conventions: https://reactrouter.com/how-to/file-route-conventions#file-route-conventions
• TanStack Start — TanStack Router File Naming Conventions: https://tanstack.com/router/v1/docs/framework/react/routing/file-naming-conventions

Full Changelog: Rel1cx/eslint-react@v2.12.4...v2.13.0

v2.12.4

Compare Source

🐞 Fixes

• Fix preact and preact/compat support in no-implicit-key rule by @​Rel1cx in #​1494

🪄 Improvements

• Refactor dom/no-unknown-property rule to fix all ESLint and TypeScript issues by @​ulrichstark in #​1490

Full Changelog: Rel1cx/eslint-react@v2.12.2...v2.12.4

v2.12.2

Compare Source

🐞 Fixes

• Reduce the sensitivity of component detection to prevent false positives in certain rules, closes #​1488 by @​Rel1cx in #​1489

Full Changelog: Rel1cx/eslint-react@v2.12.1...v2.12.2

v2.12.1

Compare Source

🐞 Fixes

• Check all union constituents and allow all types under React namespace in no-implicit-key by @​Rel1cx in #​1487

Full Changelog: Rel1cx/eslint-react@v2.12.0...v2.12.1

v2.12.0

Compare Source

🪄 Improvements

• Upgrade ESLint to v10 across the repo by @​Rel1cx in #​1486

📝 Changes you should be aware of

ESLint v10 is now supported and used throughout the repository. The minimum required ESLint version remains v8.57.0, but the project now supports and is tested against ESLint v10.

Full Changelog: Rel1cx/eslint-react@v2.11.2...v2.12.0

v2.11.2

Compare Source

🐞 Fixes

• Implement a more robust check to handle cases that getFullyQualifiedName cannot handle in no-implicit-key, closes #​1476 by @​Rel1cx in #​1480

🪄 Improvements

• Bump esbuild, node types, jsdoc plugin

Full Changelog: Rel1cx/eslint-react@v2.11.1...v2.11.2

v2.11.1

Compare Source

🐞 Fixes

• Fix React internal key checks in no-implicit-key, closes #​1476 by @​Rel1cx in #​1479
• Add no-implicit-key rule to disable-type-checked config of eslint-plugin-react-x, closes #​1477 by @​Rel1cx in #​1478

Full Changelog: Rel1cx/eslint-react@v2.11.0...v2.11.1

v2.11.0

Compare Source

✨ New

• Add RSC rules to recommended presets by @​Rel1cx in #​1475

Full Changelog: Rel1cx/eslint-react@v2.10.1...v2.11.0

v2.10.1

Compare Source

🐞 Fixes

• Relax no-implicit-key rule for React internally defined keys, closes #​1472 by @​Rel1cx in #​1474

Full Changelog: Rel1cx/eslint-react@v2.10.0...v2.10.1

v2.10.0

Compare Source

• Refactor no-implicit-key rule to use type checking by @​Rel1cx in #​1466
• Move no-unnecessary-use-ref to removed rules, closes #​1417 by @​Rel1cx in #​1471

📝 Changes you should be aware of

1. The no-implicit-key rule has been updated to use type checking and moved from recommended to type-checked presets.
2. The no-unnecessary-use-ref rule has been moved to removed rules, because the rule is hard to get right.

Full Changelog: Rel1cx/eslint-react@v2.9.4...v2.10.0

v2.9.4

Compare Source

🐞 Fixes

• Fix sub-plugin's READMEs by @​Rel1cx in #​1465

Full Changelog: Rel1cx/eslint-react@v2.9.3...v2.9.4

v2.9.3

Compare Source

📝 Changes you should be aware of

The following rules have been deprecated and will be removed in the next major version:

• no-default-props
• no-prop-types
• no-string-refs

For legacy codebases, use no-restricted-syntax as an alternative:

{
    files: ['**/*.jsx', '**/*.tsx'],
    rules: {
        "no-restricted-syntax": [
            "error",
            {
                "selector": "AssignmentExpression[operator='='][left.property.name='defaultProps']",
                "message": "[Deprecated] Use ES6 default parameters instead."
            },
            {
                "selector": "AssignmentExpression[operator='='][left.property.name='propTypes']",
                "message": "[Deprecated] Use TypeScript or another type-checking solution instead."
            },
            {
                "selector": "JSXAttribute[name.name='ref'][value.type='Literal']",
                "message": "[Deprecated] Use callback refs instead."
            }
        ]
    }
}

Full Changelog: Rel1cx/eslint-react@v2.9.2...v2.9.3

v2.9.2

🐞 Fixes

• Fix directives checks by @​Rel1cx in #​1461
• Add missing rsc plugin to all config, closes #​1462 by @​Rel1cx in #​1463

🪄 Improvements

• Separate message ids for rsc/function-definition by @​SukkaW in #​1460

Full Changelog: Rel1cx/eslint-react@v2.9.0...v2.9.2

v2.9.0

Compare Source

✨ New

• Migrate no-non-async-server-functions rule to rsc/function-definition by @​Rel1cx in #​1457
• Add a new eslint-plugin-react-rsc sub-plugin for React Server Components (RSC) rules by @​Rel1cx in #​1457
• Add a new rsc preset to enable RSC rules by @​Rel1cx in #​1457
• Add a new disable-rsc preset to disable RSC rules by @​Rel1cx in #​1457

🪄 Improvements

• Move grouped docs from the global overview to per-plugin READMEs by @​Rel1cx in #​1449

📝 Changes you should be aware of

The no-non-async-server-functions rule has been migrated to rsc/function-definition. Please update your configuration accordingly if you are using it.

Full Changelog: Rel1cx/eslint-react@v2.8.4...v2.9.0

v2.8.4

Compare Source

🐞 Fixes

• Change status of jsx-shorthand-boolean rule in migration table by @​connorshea in #​1446
• Fix rule name in docs for debug/is-from-ref by @​amir-rahmanii in #​1445
• Fix rule name in docs for no-non-async-server-functions by @​Rel1cx in #​1447
• Mark no-non-async-server-functions as experimental by @​Rel1cx in #​1448

v2.8.3

Compare Source

✨ New

• feat(#​1435): implements no-non-async-server-functions by @​SukkaW in #​1443

Full Changelog: Rel1cx/eslint-react@v2.8.1...v2.8.3

v2.8.1

Compare Source

✨ New

• Function component detection now supports identifying components that don't return a ReactNode but have a 'use memo' or 'use no memo' directive by @​Rel1cx in #​1440
  The function in below example will be detected as a function component in relevant rules:

  function App() {
    "use memo";
  }
  
  function App() {
    "use no memo";
  }

🐞 Fixes

• Skip unstable value checks when 'use memo'; is present by @​Rel1cx in #​1441

Full Changelog: Rel1cx/eslint-react@v2.8.0...v2.8.1

v2.8.0

Compare Source

✨ New

• Function component detection now supports identifying components that don't return a ReactNode but call React Hooks by @​Rel1cx in #​1438
  The function in below example will be detected as a function component in relevant rules:

  function App() {
    useEffect(() => {}, []);
  }

🐞 Fixes

• Revert no-unnecessary-key to remove constant key checking, closes #​1436 by @​Rel1cx in #​1439

Full Changelog: Rel1cx/eslint-react@v2.7.4...v2.8.0

v2.7.4

Compare Source

✨ New

• Add debug/is-from-ref rule by @​Rel1cx in #​1433

🐞 Fixes

• fix(no-leaked-conditional-rendering): support enum, closes #​1428 by @​hyoban in #​1429

🪄 Improvements

• Enhance component detection hints with array patterns and expressions by @​Rel1cx in #​1430
• Enhance rules overview page by @​Rel1cx in #​1432

Full Changelog: Rel1cx/eslint-react@v2.7.2...v2.7.3

leanix/leanix-reporting (@​leanix/reporting)

v0.4.172

Compare Source

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v5.1.4

Compare Source

Fix canSkipBabel not accounting for babel.overrides (#​1098)

When configuring babel.overrides without top-level plugins or presets, Babel was incorrectly skipped. The canSkipBabel function now checks for overrides.length to ensure override configurations are processed.

v5.1.3

Compare Source

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.0

Compare Source

Breaking changes

• The package now ships as ESM and requires ESLint 9 + node 20. Because legacy config doesn't support ESM, this requires to use flat config
• A new reactRefresh export is available and prefered over the default export. It's an object with two properties:
  • plugin: The plugin object with the rules
  • configs: An object containing configuration presets, each exposed as a function. These functions accept your custom options, merge them with sensible defaults for that config, and return the final config object.
• customHOCs option was renamed to extraHOCs
• Validation of HOCs calls is now more strict, you may need to add some HOCs to the extraHOCs option

Config example:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig(
  /* Main config */
  reactRefresh.configs.vite({ extraHOCs: ["someLibHOC"] }),
);

Config example without config:

import { defineConfig } from "eslint/config";
import { reactRefresh } from "eslint-plugin-react-refresh";

export default defineConfig({
  files: ["**/*.ts", "**/*.tsx"],
  plugins: {
    // other plugins
    "react-refresh": reactRefresh.plugin,
  },
  rules: {
    // other rules
    "react-refresh/only-export-components": [
      "warn",
      { extraHOCs: ["someLibHOC"] },
    ],
  },
});

Why

This version follows a revamp of the internal logic to better make the difference between random call expressions like export const Enum = Object.keys(Record) and actual React HOC calls like export const MemoComponent = memo(Component). (fixes #​93)

The rule now handles ternaries and patterns like export default customHOC(props)(Component) which makes it able to correctly support files like this one given this config:

{
  "react-refresh/only-export-components": [
    "warn",
    { "extraHOCs": ["createRootRouteWithContext"] }
  ]
}

[!NOTE]
Actually createRoute functions from TanStack Router are not React HOCs, they return route objects that fake to be a memoized component but are not. When only doing createRootRoute({ component: Foo }), HMR will work fine, but as soon as you add a prop to the options that is not a React component, HMR will not work. I would recommend to avoid adding any TanStack function to extraHOCs it you want to preserve good HMR in the long term. Bluesky thread.

Because I'm not 100% sure this new logic doesn't introduce any false positive, this is done in a major-like version. This also give me the occasion to remove the hardcoded connect from the rule. If you are using connect from react-redux, you should now add it to extraHOCs like this:

{
  "react-refresh/only-export-components": ["warn", { "extraHOCs": ["connect"] }]
}

npm/cli (npm)

v11.10.0

Compare Source

Features

• cf56a1e #​8899 npm trust, per-command config (@​reggi)
• cf56a1e #​8899 npm trust (@​reggi)
• 66d6e11 #​8965 add min-release-age (#​8965) (@​wraithgar)

Dependencies

• aae84bf #​8973 pacote@21.3.1
• 8bcb675 #​8973 cidr-regex@5.0.2
• f87aaab #​8973 lru-cache@11.2.6
• acec871 #​8973 ssri@13.0.1
• 1e42a86 #​8973 glob@13.0.2
• e1c08a4 #​8973 is-cidr@6.0.3
• dfb0e34 #​8973 semver@7.7.4
• 0ee7776 #​8973 which@6.0.1

Chores

• eb81df8 #​8973 dev dependency updates (@​wraithgar)
• 995e757 #​8966 Clean up some todos, add tests for previously skipped blocks (@​owlstronaut)
• workspace: @npmcli/arborist@9.3.0
• workspace: @npmcli/config@10.7.0
• workspace: libnpmdiff@8.1.1
• workspace: libnpmexec@10.2.1
• workspace: libnpmfund@7.0.15
• workspace: libnpmpack@9.1.1

isaacs/rimraf (rimraf)

v6.1.3

Compare Source

npm/node-semver (semver)

v7.7.4

Compare Source

Bug Fixes

• a29faa5 #​835 cli: pass options to semver.valid() for loose version validation (#​835) (@​mldangelo)

Documentation

• 1d28d5e #​836 fix typos and update -n CLI option documentation (#​836) (@​mldangelo)

Dependencies

• 120968b #​840 @npmcli/template-oss@4.29.0 (#​840)

Chores

• 44d7130 #​824 bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#​824) (@​dependabot[bot])
• 7073576 #​820 reorder parameters in invalid-versions.js test (#​820) (@​reggi)
• 5816d4c #​829 bump @​npmcli/template-oss from 4.28.0 to 4.28.1 (#​829) (@​dependabot[bot], @​npm-cli-bot)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10am and before 4pm every weekday" in timezone Europe/Berlin.

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.