Repository navigation
Update npm dependencies - #128
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/npm-dependencies
branch
from
November 2, 2026 05:54
fb23911 to
13a203f
Compare
renovate
Bot
force-pushed
the
renovate/npm-dependencies
branch
from
November 2, 2026 17:15
13a203f to
0852d35
Compare
renovate
Bot
force-pushed
the
renovate/npm-dependencies
branch
from
November 3, 2026 15:54
0852d35 to
46c87f5
Compare
renovate
Bot
force-pushed
the
renovate/npm-dependencies
branch
from
November 5, 2026 01:47
46c87f5 to
4fc2521
Compare
No767
approved these changes
Nov 5, 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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
6.0.3→6.0.410.13.0→10.14.01.89.0→1.90.017.13.0→17.14.026.12.1→26.13.0^0.74.0→^0.76.01.89.0→1.91.00.9.18→0.9.2212.15.0→12.16.18.72.0→8.72.1Release Notes
eslint/eslint (eslint)
v10.14.0Compare Source
Features
d23a7f9feat: fix property descriptor handling infunc-name-matching(#21400) (xbinaryx)Bug Fixes
4a12580fix: require minimatch10.2.6to avoid vulnerable brace-expansion (#21460) (lumir)827a8f3fix:no-restricted-globalscrash on global objects as property values (#21449) (xbinaryx)161558afix: handle LS, PS and empty hashbang comments (#21419) (lumir)6194939fix:no-invalid-thiscrash onaccessorfields without initializer (#21442) (xbinaryx)9155e14fix: Update @humanfs/node dependency version (#21434) (Nicholas C. Zakas)cb2b9d4fix: avoid invalid object-shorthand fixes for super methods (#21323) (dvd233)5ee3915fix: yoda invalid autofix at statement start (#21424) (Daniel Pinto)Documentation
0f94f47docs: removezh-hansfrom docs language switcher (#21437) (lumir)dab466edocs: Update README (GitHub Actions Bot)97431f8docs: replace--rulesdirwith a virtual plugin in custom rules docs (#21452) (Pixel)7697550docs: Update README (GitHub Actions Bot)0c699d5docs: Remove Tidelift commercial support (#21416) (Milos Djermanovic)0880666docs: update loadESLint() documentation for v10 (#21374) (Minseon Kim)e06fe87docs: Revise AI acknowledgment options in PR template (#21414) (Nicholas C. Zakas)Chores
0e2ab70ci: disableeslint-plugin-unicornecosystem test (#21462) (Francesco Trotta)6e3f988chore: update github/codeql-action action to v4.39.1 (#21450) (renovate[bot])a031c40chore: update ecosystem plugins (#21445) (ESLint Bot)67d2ca2chore: add troubleshooting page URL to circular fixes warning message (#21429) (Milos Djermanovic)276021dchore: update github/codeql-action action to v4.39.0 (#21432) (renovate[bot])449724echore: update ecosystem plugins (#21420) (ESLint Bot)8ffeb8cchore: update dependency prettier to v3.9.10 (#21417) (renovate[bot])oxc-project/eslint-plugin-oxlint (eslint-plugin-oxlint)
v1.90.0Compare Source
What's Changed
buildFromConfigFileby @Sysix in #808Full Changelog: oxc-project/eslint-plugin-oxlint@v1.89.0...v1.90.0
sindresorhus/globals (globals)
v17.14.0Compare Source
7abfb5dnodejs/node (node)
v26.13.0: 2026-10-28, Version 26.13.0 'Lithium' (LTS), @richardlauCompare Source
Notable Changes
This release marks the transition of Node.js 26.x into Long Term Support (LTS)
with the codename 'Lithium'. It will continue to receive updates through to
the end of April 2029.
Other than updating metadata, such as the
process.releaseobject, to reflectthat the release is LTS, no further changes from Node.js 26.12.1 are included.
If you are updating from an earlier Long Term Support release (e.g. Node.js 24
or 22 or earlier) please note that since Node.js 25 the official binaries for
Linux are linked against libatomic, which may need to be installed separately
depending on your Linux distribution.
oxc-project/oxc (oxfmt)
v0.76.0: oxfmt v0.76.0Compare Source
💥 BREAKING CHANGES
296623doxfmt: [BREAKING] Formatparser:htmlfiles byoxc_formatter_htmlish(#28273) (Yuji Sugiura)🚀 Features
336b2c1oxfmt: Support html-in-js templates closing a dynamic tag name (#28389) (Yuji Sugiura)0a42af6formatter_htmlish: Format end tags of omittedhtml,headandbody(#28388) (Yuji Sugiura)44d8c2bformatter_htmlish: Implement HTML-ish formatterHtmlvariant (#28272) (Yuji Sugiura)36e5ddboxfmt: Add debug span for reading files (#28204) (leaysgur)🐛 Bug Fixes
dbcc358formatter: Keep arrow conditional body parens before a leadingfunction/class(#28710) (Yuji Sugiura)fef809aformatter_htmlish: Handle XHTML (#28703) (leaysgur)f3dd201formatter_htmlish: Keep SVG text underxml:space="preserve"as written (#28382) (Yuji Sugiura)fb3aefaformatter: Keep source parens around html-in-js placeholders past comments (#28381) (Yuji Sugiura)e738daeformatter: Quote keys added in an HTML event handler with single quotes (#28380) (Yuji Sugiura)2e7a629oxfmt: Format HTML in a<script>body as an embedded part (#28379) (Yuji Sugiura)f00862bformatter: Keep parens around a generic function type in a type assertion (#28173) (vidigoat)9ead5c4formatter: Handlethis.bandsuper.blikefoo.b(#28200) (leaysgur)72a54cfformatter: Break parens of(a + b)[c]like(a + b).c(#28199) (leaysgur)b8f4f34formatter: Printx.bandx.#bsamely (#28193) (leaysgur)9ddccb7formatter: Keep parens for private field (#28188) (leaysgur)⚡ Performance
b6f1ac9formatter_markdown: Bump parser to 0.0.4 and skip unread work (#28713) (leaysgur)633ee96formatter_css: Useu32spans (#28708) (leaysgur)f680ee1formatter_yaml: Usemultilineflag for flow scalars (#28707) (leaysgur)ff7c203formatter_css: Avoid repeated scans and allocations in values (#28706) (leaysgur)7cd46cbformatter_htmlish: Search script end tags by<in embedded (#28704) (leaysgur)46f8efdformatter_graphql: Print block string lines borrowed from the source (#28701) (leaysgur)dce1485formatter_htmlish: Skip escaping attr values without the chosen quote (#28700) (leaysgur)e9392c8formatter_core: Search line terminators with memchr (#28699) (leaysgur)ceb26beformatter_htmlish: Usecharto escape attr quotes (#28697) (leaysgur)8239dacparser: Replace dragonbox_ecma with zmij_ecma (#28282) (Boshen)📚 Documentation
303d9e8formatter: Strengthenstart-token-no-double-parensrationale (#28711) (Yuji Sugiura)a82ce83oxfmt: Update unclassified divergence (#28685) (Yuji Sugiura)7f18c20formatter_htmlish: Noteclassandsrcsetare formatted withembeddedLanguageFormatting: off(#28465) (Yuji Sugiura)01ed68aoxfmt,formatter_htmlish,formatter: Clean up behavior comments (#28384) (Yuji Sugiura)a363c27formatter_css,formatter_yaml: Point parser citations at AGENTS.md (#28466) (Yuji Sugiura)6586050formatter_core: Document tab width in text width policy (#28393) (leaysgur)49fbffbformatter_core: Tighten FORMATTER_POLICY (#28206) (leaysgur)v0.75.0: oxfmt v0.75.0Compare Source
🐛 Bug Fixes
5042019formatter: Keep fill layout for array with comment after [ (#28170) (leaysgur)9d37ff6formatter: Use position-based comment checks for concise arrays (#28169) (leaysgur)016c4a2formatter: Keep a comment before}inside a JSX spread child (#28103) (vidigoat)190bb1eformatter: Keep parens around an instantiation expression ending an operand through any tight parent (#28168) (leaysgur)a5314a1formatter: Keep;beforeinandinstanceofclass members (#28166) (leaysgur)3a56e7cformatter: Keep closing HTML comments at the start of a line (#28064) (Cameron)23d23d6formatter_markdown: Honor range ignore inside directives (#28164) (leaysgur)5f1fd3dformatter: Measure width heuristics by display width (#28098) (leaysgur)a5a52cfformatter: Keep parens around privateinexpressions (#28096) (leaysgur)999496eformatter: Measure a short key by its display width (#28026) (vidigoat)7e9aa44formatter: Keep parens around a looser operand of an instantiation expression (#28025) (vidigoat)6912d1fformatter: Keep an arrow signature that exactly fills the line for any body (#27989) (leaysgur)eb1d9f9formatter_core: Count a flatlinespace infitsonly when text follows (#27987) (leaysgur)⚡ Performance
1ed93afdata_structures: Copy short strings without a memcpy call (#27953) (leaysgur)7948f0bformatter_core: ShrinkFormatElementto 16B (#28012) (leaysgur)788af22formatter: KeepAstNodes on the stack, and only chain links in the arena (#27963) (leaysgur)📚 Documentation
068a8eaformatter: Fix up wording (#28167) (leaysgur)db55461formatter_core: Document text width divergence (#28095) (leaysgur)880d229formatter: Add vitest-test-call to known divergences (#28006) (leaysgur)oxc-project/oxc (oxlint)
v1.91.0Compare Source
🚀 Features
419c1b0linter: Add allow and allowPattern options to react/capitalized-calls (Christian Vuerings)v1.90.0Compare Source
🚀 Features
831cdf1oxlint: Require mininum oxlint-tsgolint version v7.0.2005 (#28118) (camc314)d1b00f4linter/typescript: Implement no-unsafe-enum-assignment rule (#28117) (camc314)165c91flinter/typescript/await-thenable: SupportallowMixedPromiseArraysoption (#28116) (camc314)millionco/react-doctor (oxlint-plugin-react-doctor)
v0.9.22Compare Source
Patch Changes
ad51b5aThanks @aidenybai! - Treat an effect cleanup that only reads a proven local runtime binding as empty. Preserve cleanup exemptions for global identifiers and member reads that can run getters, and keep no-op filtering conservative in other rules.no-mirror-prop-effect,no-event-trigger-state,no-effect-event-handler,no-effect-chainandrendering-hydration-no-flickeralso stop skipping effects with proven empty or read-only inline cleanups. Unknown cleanup factories and other effectful returns remain conservative.v0.9.21Compare Source
Patch Changes
#2320
5a2c6f5Thanks @aidenybai! - Report an unguardeduseReducerdispatch afterawaitor inside a microtask or Promise callback when it goes through a transparent local setter helper, such asqueueMicrotask(() => assign(dispatch, action)), exactly where the direct dispatch is reported. Onlyno-set-state-after-await-in-effectaccepts the forwarded dispatch, because it already counts a direct dispatch. The prop-change rules, which compare writes againstuseStateinitializers, stay unchanged. Imported, reassigned, asynchronous, deferred and conditional helpers, and reassigned dispatch bindings, stay outside the proof.#2319
39152dcThanks @aidenybai! - Reportreact-hooks-js/set-state-in-effectwhen an effect updates state synchronously through a transparent local setter helper, such asuseEffect(() => assign(setValue, next)), which React Compiler does not follow. A newforwarded-set-state-in-effectrule finds the write with the forwarded setter proof, runs only when the compiler rule is enabled, and React Doctor reports its finding under the compiler's rule key, message and docs link, soreact-hooks/set-state-in-effectdisable comments, ignores and scoring treat it like the compiler finding. Compiler-visible synchronous setter calls retain duplicate suppression. Ref-derived measurements and guarded ref writes remain allowed. Imported, reassigned, asynchronous, deferred, conditional and multi-statement forwarding helpers stay outside the proof.v0.9.20Compare Source
Patch Changes
#2317
2c5d72cThanks @aidenybai! - Report an unguarded state update afterawaitor inside a microtask or Promise callback when it goes through a transparent local setter helper, such asqueueMicrotask(() => assign(setValue, next)), exactly where the direct setter call is reported. Cleanup guards still protect the forwarded write. Imported, reassigned, asynchronous, deferred, conditional, and multi-statement helpers stay outside the proof. Preserve transparent TypeScript setter arguments and implicit undefined writes, and exclude bound/call/apply argument shifts from the forwarding proof.Keep resource lifecycle exemptions when the same setter is forwarded through immutable aliases, and register the deferred-write rule in cross-file cache metadata.
#2315
8a7c60aThanks @aidenybai! - Report state adjusted after a prop change through a transparent local setter helper, such asassign(setValue, ""), exactly where the direct setter call is reported, including functional updaters and layout effects. Evaluate the forwarded write at its call site for the released object URL, portal mount, request map, resource lifecycle, and external work checks. Imported, reassigned, asynchronous, deferred, conditional, and multi-statement helpers stay outside the proof.Preserve resource lifecycle and asynchronous loading exemptions when related event or completion writers also use transparent setter helpers.
#2316
b713862Thanks @aidenybai! - Report an effect that resets all state after a prop change through a transparent local setter helper, such asassign(setKey, ""), exactly where the direct reset is reported, including layout effects. A reload forwarded through the same helper from an asynchronous callback now counts as a loading lifecycle, and a handler that writes through the helper keeps the hidden-until-reset exemption. Imported, reassigned, asynchronous, deferred, conditional, and multi-statement helpers stay outside the proof.Keep setter identity stable across immutable aliases when counting reset state and recognizing asynchronous reloads. Resource lifecycle handlers retain their exemptions when their writes are forwarded through the same proven helper.
v0.9.19Compare Source
Patch Changes
#2000
9a79847Thanks @aidenybai! - Let rules declare the code that owns a finding separately from its diagnostic location. With--scope contextual,exhaustive-depsnow reports existing dependency findings when their hook call or resolved local callback changes. Ownership survives lint-cache replay and stays out of public JSON reports and score requests.Add JSX element scope for
alt-textandclick-events-have-key-events, and function scope forrules-of-hooks. Existing scan defaults and other scopes are unchanged.#2311
813bd63Thanks @aidenybai! - Recognize synchronous derived-state writes through transparent local helpers that receive a React state setter. Preserve external, deferred, mutable, and independently editable state, including event writes through readonly setter aliases for direct and forwarded effect writes. Compare forwarded values with their existing state initializer. Withhold the forwarding proof for reassigned helpers and parameters whose defaults or destructuring can perform additional work.#2313
be55f78Thanks @aidenybai! - Detect unguarded state updates in inline microtask and proven native Promise callbacks started by effects with changing dependencies. Preserve cleanup guards, stable dependencies, and opaque or shadowed thenables.Exclude inert generator callbacks and mutated or escaped Promise receivers, and cache immutable provenance checks for shared Promise bindings.
#2312
e5c7c99Thanks @aidenybai! - Detect redundant state derivation, initialization, adjustment, and resets in ReactuseLayoutEffect, including imported aliases. Preserve layout measurement and resource lifecycle exemptions, and describe avoidable renders without implying stale content must be painted.#2308
a4bcd7fThanks @NisargIO! - Stop treating an empty effect cleanup as a real one.return () => {},return () => undefined, a directconstfunction binding, orflag ? () => {} : undefinedno longer silencesno-adjust-state-on-prop-change,no-chain-state-updates,no-effect-event-handler,no-event-handler,no-pass-data-to-parent, or the derived-state rules' cleanup-managed state check. Cleanups that do work during parameter evaluation and disposer calls opposite inline or named empty functions still exempt the effect. Mutable bindings and unproven callback factories retain the existing conservative exemption.#2011
84ad0c8Thanks @skoshx! - Fixunsafe-json-in-htmlfalse positive forJSON.stringify().replaceAll("<", "\\u003c")The
unsafe-json-in-htmlrule now recognizes.replaceAll("<", "\\u003c")as a safe escape pattern, equivalent to the already-recognized.replace(/</g, "\\u003c")form. This resolves false positives when developers use the more explicit.replaceAllmethod to escape less-than characters in JSON-LD or other JSON embedded in HTML/script tags.#2309
95cd1d4Thanks @aidenybai! - Detect missing cleanup for native timers called through globalThis, window, self, global, and proven constant aliases. Recognize matching qualified clearInterval and clearTimeout calls while preserving shadowed receiver and timer handle checks. Exclude qualified timer methods that have been overwritten, deleted, or updated, and never count an overridden clear method as cleanup.#2310
3fd747eThanks @aidenybai! - Detect render-time ref.current writes made through Object.assign while preserving predictable guarded initialization and deferred effect or event writes. Keep semantic analysis lazy for unrelated calls. Exclude calls to an overridden Object.assign.#1983
a1df4e5Thanks @skoshx! - Skip .open-next build output in security scanThe security scan now skips
.open-next/directories (OpenNext build output) the same way it skips.next/and.vercel/, preventing false positive security findings from bundled library code.pnpm/pnpm (pnpm)
v12.16.1: pnpm 12.16.1Compare Source
This release fixes
pnpm installhanging on a cold store in workspaces that install Cargo crates, andpnpm packshipping a file thatfilesexcludes by name.Patch Changes
pnpm installno longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.pnpm packandpnpm publishnow apply afilesentry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as!dist/index.js, stays out even when a laterdist/**matches it. A file named by its path, such aslib/secret.js, ships even when a later!lib/*.jsmatches it.pnpm installno longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.pnpm installnow relinks a command that a workspace project renames into the projects that depend on it whensharedWorkspaceLockfileisfalsepnpm/tasks#224.pnpm installandpnpm rebuildnow refresh privately hoisted.binshims innode_modules/.pnpm/node_modules/.binafter a dependency build replaces a script target with a native executable #17402.pnpm installnow reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.Commands,
pnpm --version,pnpm self-update, and invocations with unknown flags now apply the samepackageManageranddevEngines.packageManagersettings when switching to the pinned pnpm version or recording it inpnpm-lock.yaml.--config.<key>flags andlockfileDirnow reach the version switch and lockfile sync on every entry point. Unreadable settings inpnpm-workspace.yamlor the globalconfig.yamlthat do not affect the pin decision no longer block the version switch pnpm/tasks#222.pnpm now accepts the
--cache-dir <dir>flag, as inpnpm install --cache-dir /tmp/pnpm-cache#17422.When the version or range given to
pnpm unpublishmatches every published version, the error now says so and shows the same command with--force. Before, the error suggested runningpnpm unpublish <pkg>@<version>, the command that had just failed.Platinum Sponsors
Gold Sponsors
v12.16.0: pnpm 12.16Compare Source
This release adds a global
--env-fileflag, updates to a symlinkedpnpm-lock.yaml, andpnpm setup --no-modify-path. It also fixes two security issues, in zstd decompression and in signing.Minor Changes
Added a repeatable global
--env-file <path>flag to load environment variables from dotenv-style files before running a command. Later files override earlier files, variables already in the environment are preserved, and loaded variables are visible to user-level.npmrcinterpolation and lifecycle scripts #7111.pnpm can now update a
pnpm-lock.yamlthat is a symlink. List the directories the lockfile may link into in thesymlinkedLockfileTargetDirssetting, in the global config or withPNPM_CONFIG_SYMLINKED_LOCKFILE_TARGET_DIRS. pnpm writes the update to the file the symlink points to if that file is inside one of these directories. The symlink stays in place. pnpm ignores this setting inpnpm-workspace.yaml#17222.Added a
--no-modify-pathoption topnpm setup. It installs pnpm without adding it toPATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged.pnpm setupthen prints the lines to add yourself get.pnpm.io#37.Patch Changes
Security
Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #17388.
Signing in pnpm and pnpr no longer uses arithmetic that may leak the private key through timing. This covers shared artifacts, OCI registry tokens, and OIDC login state advisory.
Installing packages
A dependency symlink that pnpm cannot point at the wanted target now fails the install with an error that names the link. This happens when the filesystem still serves the old link after pnpm removed it, as a
node_modulesserved by a virtual filesystem does. pnpm used to remove the link again without end and crashed with a segmentation fault once the thread ran out of stack.Concurrent workspace installs no longer lose store-index rows when initializing the shared SQLite index #17388.
Agent skill links now keep the same target across installs when a package version is installed with several sets of peer dependencies. An install no longer fails with
ERR_PNPM_AGENT_SKILL_PATH_OCCUPIEDon a skill link that pnpm created for another of those copies #17319.pnpm now fails at once, without retrying, when a downloaded package archive contains a rejected entry path #17205.
pnpm now builds a git-hosted dependency in every new location it links the dependency into, such as a new global virtual store slot or a fresh
node_modules. When the side-effects cache holds the build output, pnpm restores it from there. Before, only the install that fetched the dependency built it. This also fixes dependencies that are already in the store #17224.Changes a
preResolutionhook makes to the lockfiles now take effect. The hook now also runs when pnpm installs from an up-to-date lockfile. An error thrown by the hook now fails the install.A custom fetcher in the pnpmfile can now call
fetchers.directoryto fetch a package from a local directory. The call rejects withERR_PNPM_TARBALL_INTEGRITYif the lockfile pins an archive integrity for the package. Previously, callingfetchers.directoryfailed with aTypeError.packageImportMethod: copynow also applies to packages that have lifecycle scripts or patches. On a filesystem that supports block cloning, such as ReFS or a Dev Drive on Windows, these packages were cloned #17195.With
nodeLinker: hoistedandautoInstallPeers: false, a package that workspace projects use with different peer versions is now installed once per peer variant, so each project's copy resolves that project's peer #17395.Under
nodeLinker: hoisted,pnpm installnow leaves a patched package that is already in place alone. The same holds for a package whose peers include a patched package, such as every package peering on a patchedreact-native#17188.With
nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package innode_modules.Repeat installs and changed settings
A repeat
pnpm installnow acts on a change to these settings. Before, it reported "Already up to date".storeDirorvirtualStoreDir: it recreatesnode_modules.globalVirtualStoreDir: it links the packages from the new directory.virtualStoreDirMaxLength: it renames the virtual store directories.dangerouslyAllowAllBuildsturned on: it runs the builds it skipped.trustLockfileturned off: it verifies the lockfile.pnpm add,pnpm remove, andpnpm updatenow fail ifnode_modulesdoes not match the current settings. Runpnpm installto recreate it. Previously, these commands removed and reinstallednode_moduleswithout asking. They report:ERR_PNPM_UNEXPECTED_STOREifnode_moduleswas linked from a different store.ERR_PNPM_UNEXPECTED_VIRTUAL_STOREif it was linked from a different virtual store directory.ERR_PNPM_MODULES_BREAKING_CHANGEif it was installed by an incompatible pnpm version, or ifnode_modules/.modules.yamlcannot be read.ERR_PNPM_NODE_LINKER_DIFFif it was installed with a differentnodeLinker.pnpm updatenow also fails withERR_PNPM_HOIST_PATTERN_DIFFand the other errorspnpm addreports for a changed hoist pattern orvirtualStoreDirMaxLength.An install filtered to some workspace projects now fails if
node_moduleswas installed with a differentnodeLinker,hoistPattern,publicHoistPattern, store, or virtual store. Before, it recreatednode_modulesand left the projects it skipped without their dependencies. Apnpm installof the whole workspace still recreatesnode_modulespnpm/tasks#217.pnpm installand theverifyDepsBeforeRuncheck now notice an edited patch file whensharedWorkspaceLockfileisfalse.pnpm installnow takes its fast path in a workspace withpatchedDependencieswhen the previous install ran with another major version of pnpm.pnpm installnow relinks the bins of a workspace package when itsbinfield changes, including with--frozen-lockfileand an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #17324.pnpm installnow removes command shims fromnode_modules/.binwhen a workspace dependency renames or removes an entry from itsbinfield pnpm/tasks#211.Resolving dependencies and the lockfile
A package that a plain range and a
<prefix>:specifier both resolve from one registry is now recorded once inpnpm-lock.yamland installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, throughprefixinregistriesor throughnamedRegistries, the package is keyed<name>@<prefix>:<version>however its dependency was written: with the prefix, as a plain range its scope routes to that registry, or through the default registry. Before, the plain range was keyed<name>@<version>, so one tarball was installed twice andinstanceofchecks and module singletons broke between the two copies. The same name and version served by two registries still get separate entries. When several prefixes declare one registry, its packages are keyed by the lexicographically smallest prefix.If a scope you route reaches a registry that also declares a prefix, your next
pnpm installre-keys those entries, which shows up as a lockfile diff. Commit it.pnpm install --frozen-lockfileinstalls the lockfile as recorded.pnpm installnow resolves a scope's packages again when the scope is routed to another registry inregistries. Before, the lockfile kept the versions and integrity resolved from the old registry, so the install failed when the new registry did not serve a locked version or served different content. pnpm records in the workspace state which registry each scope routed to, so a fresh clone without that record installs the lockfile as recorded. Changing the default registry resolves nothing again, andpnpm install --frozen-lockfileis unchanged.When
autoDedupeis off, a workspace project's dependencies now resolve from its own ranges, like they do withsharedWorkspaceLockfile: false. Previously, another projConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.