Skip to content

Update npm dependencies - #92

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/npm-dependencies
Aug 9, 2026
Merged

Update npm dependencies#92
renovate[bot] merged 1 commit into
mainfrom
renovate/npm-dependencies

Conversation

@renovate

@renovate renovate Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
eslint (source) 10.8.010.8.1 age confidence devDependencies patch
eslint-plugin-oxlint 1.76.01.77.0 age confidence devDependencies minor
eslint-plugin-perfectionist (source) 5.10.05.10.1 age confidence devDependencies patch
eslint-plugin-react-dom (source) 5.18.15.18.3 age confidence devDependencies patch
eslint-plugin-react-jsx (source) 5.18.15.18.3 age confidence devDependencies patch
eslint-plugin-react-naming-convention (source) 5.18.15.18.3 age confidence devDependencies patch
eslint-plugin-react-x (source) 5.18.15.18.3 age confidence devDependencies patch
globals 17.8.017.9.0 age confidence devDependencies minor
node (source) 26.5.126.7.0 age confidence tools minor
oxfmt (source) ^0.61.0^0.62.0 age confidence devDependencies minor
oxlint (source) 1.76.01.77.0 age confidence devDependencies minor
pnpm (source) 11.18.011.20.0 age confidence tools minor
typescript-eslint (source) 8.65.08.66.0 age confidence devDependencies minor

Release Notes

eslint/eslint (eslint)

v10.8.1

Compare Source

Bug Fixes

  • 18eb0a7 fix: prevent ASI hazard in no-unused-labels autofix (#​21173) (dongkyu lee)
  • 151ba3f fix: false positives in getter-return and accessor-pairs (#​21163) (Grit)
  • 6898df9 fix: ignore meta-property names in id-denylist (#​21166) (Pixel)
  • 4d7db66 fix: ignore meta-property names in id-match (#​21167) (Pixel)
  • 677214e fix: handle ASI hazards in no-unused-vars removeVar suggestion (#​20935) (kuldeep kumar)

Documentation

  • 7d0cbf8 docs: Update README (GitHub Actions Bot)
  • 0a05812 docs: add missing backticks to no-duplicate-imports.js (#​21183) (Lee Daeun)
  • 678c90b docs: Update README (GitHub Actions Bot)
  • 8a10424 docs: Update README (GitHub Actions Bot)
  • 69bb948 docs: Update README (GitHub Actions Bot)

Chores

oxc-project/eslint-plugin-oxlint (eslint-plugin-oxlint)

v1.77.0

Compare Source

What's Changed

Full Changelog: oxc-project/eslint-plugin-oxlint@v1.76.0...v1.77.0

azat-io/eslint-plugin-perfectionist (eslint-plugin-perfectionist)

v5.10.1

Compare Source

compare changes

🐞 Bug Fixes
  • Fix crash in typescript 7
    (fbbc372)
  • Fix complex comments cases not being auto-fixed correctly
    (7a35d8b)
  • Respect ignored callback dependencies in nested calls
    (c9a119e)
  • Take into account extended tsconfigs
    (93a267e)
❤️ Contributors
Rel1cx/eslint-react (eslint-plugin-react-dom)

v5.18.3

Compare Source

🐞 Fixes
  • react-x/no-nested-component-definitions: narrowed the with* HOC detection in the fallback name resolution to well-known wrappers only (react-router v5's withRouter, Formik's withFormik, and recompose's withProps, withState, withHandlers, and withLifecycle) — custom HOCs following the with* naming convention are no longer treated as component wrappers. (#​1929)
🏗️ Internal
  • Bumped typescript-eslint to 8.66.0 and next to 16.3.0.

Full Changelog: Rel1cx/eslint-react@v5.18.2...v5.18.3

v5.18.2

Compare Source

🐞 Fixes
  • react-x/no-nested-component-definitions: fixed a regression where nested components wrapped in useCallback (e.g. const C = useCallback(() => <div />, []);) were no longer reported — the rule now resolves the component name through well-known component wrappers (memo, forwardRef, useCallback, observer, react-redux's connect, Relay's create*Container helpers, Apollo's graphql, and with* HOCs, including curried forms like connect(...)(Component)) up to the enclosing variable declarator, and no longer misreports array method callbacks (flatMap, forEach, reduce, etc.) in list rendering patterns. (#​1928, closes #​1927)
🏗️ Internal
  • Bumped effect to 3.22.1, eslint-plugin-jsdoc to 63.3.3, textlint to 15.8.0, js-yaml to 4.3.1, axios to 1.19.0, nx to 23.1.1, vite to 8.2.0, @vitejs/plugin-react to 6.0.5, fumadocs to 16.14.0, fumadocs-mdx to 15.2.2, preact to 10.29.8, globals to 17.9.0, lucide-react to 1.28.0, @types/react to 19.2.18, @types/react-dom to 19.2.4, and pnpm to 11.20.0.

Full Changelog: Rel1cx/eslint-react@v5.18.1...v5.18.2

sindresorhus/globals (globals)

v17.9.0

Compare Source

nodejs/node (node)

v26.7.0: 2026-08-05, Version 26.7.0 (Current), @​aduh95

Compare Source

Notable Changes
  • [58717685a1] - (SEMVER-MINOR) crypto: support loading private keys through STORE loaders (Filip Skokan) #​63949
  • [44b940ee8c] - crypto: update root certificates to NSS 3.125 (Node.js GitHub Bot) #​64746
  • [c1e4f7365e] - (SEMVER-MINOR) lib: add perfetto support (Chengzhong Wu) #​64565
  • [11c2f9c642] - (SEMVER-MINOR) module: implement Symbol.dispose in ModuleHooks (Remco Haszing) #​63928
  • [a646319f61] - (SEMVER-MINOR) test_runner: add support for --test-coverage-include-all (avivkeller) #​64830
Commits
oxc-project/oxc (oxfmt)

v0.62.0

Compare Source

🐛 Bug Fixes
oxc-project/oxc (oxlint)

v1.77.0

Compare Source

🐛 Bug Fixes
  • 5c0fa61 linter/eslint/no-warning-comments: Unify config structs and remove manual options docs (#​25151) (Mikhail Baev)
📚 Documentation
  • 9dc7756 linter/typescript/no-unnecessary-condition: Clarify options (#​25110) (camc314)
pnpm/pnpm (pnpm)

v11.20.0: pnpm 11.20

Compare Source

Minor Changes

  • Security fix. Affects projects using namedRegistries on pnpm 11.1.0–11.19.x. It is semi-breaking for those projects — see "If you use named registries" below.

    The lockfile recorded no marker for which registry a package came from. Packages were keyed by name@version alone, and entry lookup went through refToRelative(ref, name), so a dependency you declared against one registry could be satisfied by an entry that was actually resolved from another. When two registries served the same name and version, both collapsed onto a single packages: entry and whichever resolved first decided the tarball every consumer got.

    That is a package-substitution risk: a package you expect from your private registry could be installed from a different registry that publishes the same name and version, and the lockfile recorded nothing that would let you tell.

    Packages resolved from a named registry are now recorded under registry-qualified keys (<name>@<registryName>:<version>, e.g. foo@work:1.0.0), so each registry gets its own entry and the lockfile pins which one a dependency came from.

    The lockfile format version is unchanged. Registry-qualified keys appear only for packages resolved from a named registry, so a project that does not use namedRegistries sees no difference, and older pnpm versions keep reading the file.

If you use named registries

Your next non-frozen install re-keys those entries, which shows up as a lockfile diff. Commit it — that diff is the fix being applied. Review it: an entry that moves to a registry you did not expect is worth investigating.

Everyone working on the project should be on this version or newer before you do. An older pnpm reads the re-keyed lockfile fine — frozen installs are unaffected — but it does not produce registry-qualified keys itself, so any install that updates the lockfile writes those entries back to the old shape, and the next install on a current pnpm re-qualifies them. The result is a lockfile that flips back and forth, and while it is in the old shape the project is exposed again. Because the lockfile format version is deliberately unchanged, pnpm cannot detect this and warn you about it.

There is no setting to keep the old behavior: the old shape is the vulnerability.

Tarball URLs that follow the standard registry layout are no longer written to the lockfile for named-registry packages; they are recomputed from the namedRegistries setting on demand.

To use named registries, map your aliases in pnpm-workspace.yaml:

namedRegistries:
  work: https://npm.enterprise.example.com/
New built-in npmjs: alias

npmjs:

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 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.

@renovate
renovate Bot requested a review from No767 as a code owner August 9, 2026 03:47
@renovate
renovate Bot enabled auto-merge (squash) August 9, 2026 03:47
@renovate
renovate Bot merged commit 9d25e6d into main Aug 9, 2026
1 check passed
@renovate
renovate Bot deleted the renovate/npm-dependencies branch August 9, 2026 03:50
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.

1 participant