You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The merged Post takes title: String and content: Int from the second schema, keeps published from the first, and adds fieldA / fieldB. Types that exist on only one schema, such as User on the first, stay.
The same callback applies to field arguments. Returning the incoming field uses the second schema's argument types and still keeps arguments that exist on only one side. Returning the existing field with reverseArguments: true keeps the first schema's argument types and still appends new arguments.
#86066da2904 Thanks @ardatan! - loadDocuments / loadTypedefs now accept errorHandling so a single invalid file does not have to hide the rest of the load.
A glob that mixes a valid operation with broken SDL used to throw the first Syntax Error and drop every other file:
Source now has an optional error field. @graphql-tools/graphql-file-loader and @graphql-tools/code-file-loader honor the same option. CodeFileLoader's existing noSilentErrors default is unchanged unless errorHandling is set.
Custom loader failures and incomplete inline documents (query Foo {) follow the same option. errorHandling: 'throw' raises the first failure, not AggregateError.
Patch Changes
#85887770067 Thanks @ardatan! - rewireTypes (used by mapSchema and addTypes) now recreates only the types that actually reference a replaced type.
mapSchema already changes just the mapped types. rewireTypes then walked every type and built a new GraphQLObjectType / enum / scalar so field pointers stayed consistent. That is correct, and it is overkill when a pipeline maps one type on a large schema: unrelated types, unused enums, and unused scalars were cloned on every pass.
The crawl now finds types whose field, argument, interface, or union members point at a different object than the type map (including wrapper types created during mapping), then rebuilds only that set. Specified directives stay as-is. Types that do not reach a replacement keep the same JavaScript object.
createStub returns the graphql-js specified scalars for String / ID / Int / Float / Boolean instead of building an object or input with that name. Stitch typeFromAST uses createStub for every field type.
constschema=buildSchema(/* GraphQL */` scalar Unused enum Color { RED } type Query { foo: Foo } type Foo { id: ID }`)constmapped=mapSchema(schema,{[MapperKind.OBJECT_TYPE]: type=>type.name==='Foo'
? newGraphQLObjectType({ ...type.toConfig(),description: 'mapped'})
: undefined,})mapped.getType('Unused')===schema.getType('Unused')mapped.getType('Color')===schema.getType('Color')
#8608f956bfe Thanks @ardatan! - transformInputValue now keeps falsy list items when GraphQL coerces a singleton into a list.
A [String] / [Int] / [Boolean] field can receive "", 0, or false instead of a one-element array. The previous asArray helper treated those as empty and produced [], so rename and other input transforms dropped a valid value. null is still returned as-is. A real list is still walked item by item.
This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.
Patch Changes
pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.
pnpm pack and pnpm publish now apply a files entry 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 later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.
pnpm install no 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 install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is falsepnpm/tasks#224.
pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #17402.
pnpm install now 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 same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.
pnpm now accepts the --cache-dir <dir> flag, as in pnpm install --cache-dir /tmp/pnpm-cache#17422.
When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. Before, the error suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.
This release adds a global --env-file flag, updates to a symlinked pnpm-lock.yaml, and pnpm 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 .npmrc interpolation and lifecycle scripts #7111.
pnpm can now update a pnpm-lock.yaml that is a symlink. List the directories the lockfile may link into in the symlinkedLockfileTargetDirs setting, in the global config or with PNPM_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 in pnpm-workspace.yaml#17222.
Added a --no-modify-path option to pnpm setup. It installs pnpm without adding it to PATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged. pnpm setup then 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_modules served 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_OCCUPIED on 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 preResolution hook 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.directory to fetch a package from a local directory. The call rejects with ERR_PNPM_TARBALL_INTEGRITY if the lockfile pins an archive integrity for the package. Previously, calling fetchers.directory failed with a TypeError.
packageImportMethod: copy now 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: hoisted and autoInstallPeers: 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 install now 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 patched react-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 in node_modules.
Repeat installs and changed settings
A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".
storeDir or virtualStoreDir: it recreates node_modules.
globalVirtualStoreDir: it links the packages from the new directory.
virtualStoreDirMaxLength: it renames the virtual store directories.
dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.
trustLockfile turned off: it verifies the lockfile.
pnpm add, pnpm remove, and pnpm update now fail if node_modules does not match the current settings. Run pnpm install to recreate it. Previously, these commands removed and reinstalled node_modules without asking. They report:
ERR_PNPM_UNEXPECTED_STORE if node_modules was linked from a different store.
ERR_PNPM_UNEXPECTED_VIRTUAL_STORE if it was linked from a different virtual store directory.
ERR_PNPM_MODULES_BREAKING_CHANGE if it was installed by an incompatible pnpm version, or if node_modules/.modules.yaml cannot be read.
ERR_PNPM_NODE_LINKER_DIFF if it was installed with a different nodeLinker.
pnpm update now also fails with ERR_PNPM_HOIST_PATTERN_DIFF and the other errors pnpm add reports for a changed hoist pattern or virtualStoreDirMaxLength.
An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modulespnpm/tasks#217.
pnpm install and the verifyDepsBeforeRun check now notice an edited patch file when sharedWorkspaceLockfile is false.
pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.
pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and 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 install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field 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 in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in `regist
[!IMPORTANT]
✂ PR body was truncated to here.
Configuration
📅 Schedule: (UTC)
Branch creation
At any time (no schedule defined)
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
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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:
10.0.6→10.0.710.0.8^11.0.6→^11.0.711.0.813.1.3→13.2.013.2.1^5.9.0→^5.9.15.9.0→5.9.15.9.0→5.9.16.42.1→6.44.06.44.124.22.1→24.22.212.15.0→12.16.112.15.0→12.16.1Release Notes
ardatan/graphql-tools (@graphql-tools/merge)
v10.0.7Compare Source
Patch Changes
6da2904,7770067,f956bfe]:ardatan/graphql-tools (@graphql-tools/schema)
v11.0.7Compare Source
Patch Changes
#8601
902d870Thanks @ardatan! -mergeSchemasandmakeExecutableSchemanow acceptonFieldTypeConflict, the same callbackmergeTypeDefsalready had.When two schemas define the same field with different types, default merge throws. When only nullability differs, it keeps the earlier type.
content: String!vscontent: Intthrows.title: String!vstitle: StringkeepsString!.The merged
Posttakestitle: Stringandcontent: Intfrom the second schema, keepspublishedfrom the first, and addsfieldA/fieldB. Types that exist on only one schema, such asUseron the first, stay.The same callback applies to field arguments. Returning the incoming field uses the second schema's argument types and still keeps arguments that exist on only one side. Returning the existing field with
reverseArguments: truekeeps the first schema's argument types and still appends new arguments.Updated dependencies [
6da2904,7770067,f956bfe]:ardatan/graphql-tools (@graphql-tools/utils)
v13.2.0Compare Source
Minor Changes
#8606
6da2904Thanks @ardatan! -loadDocuments/loadTypedefsnow accepterrorHandlingso a single invalid file does not have to hide the rest of the load.A glob that mixes a valid operation with broken SDL used to throw the first
Syntax Errorand drop every other file:errorHandlingchooses what happens next. The default is unchanged (throwthe first error).aggregatewaits until every source is attempted, then throwsAggregateErrorwith each parse/load failure:returndoes not throw. Failed sources stay in the result as{ location, error }without adocument, next to the sources that parsed:Sourcenow has an optionalerrorfield.@graphql-tools/graphql-file-loaderand@graphql-tools/code-file-loaderhonor the same option.CodeFileLoader's existingnoSilentErrorsdefault is unchanged unlesserrorHandlingis set.Custom loader failures and incomplete inline documents (
query Foo {) follow the same option.errorHandling: 'throw'raises the first failure, notAggregateError.Patch Changes
#8588
7770067Thanks @ardatan! -rewireTypes(used bymapSchemaandaddTypes) now recreates only the types that actually reference a replaced type.mapSchemaalready changes just the mapped types.rewireTypesthen walked every type and built a newGraphQLObjectType/ enum / scalar so field pointers stayed consistent. That is correct, and it is overkill when a pipeline maps one type on a large schema: unrelated types, unused enums, and unused scalars were cloned on every pass.The crawl now finds types whose field, argument, interface, or union members point at a different object than the type map (including wrapper types created during mapping), then rebuilds only that set. Specified directives stay as-is. Types that do not reach a replacement keep the same JavaScript object.
createStubreturns the graphql-js specified scalars forString/ID/Int/Float/Booleaninstead of building an object or input with that name. StitchtypeFromASTusescreateStubfor every field type.#8608
f956bfeThanks @ardatan! -transformInputValuenow keeps falsy list items when GraphQL coerces a singleton into a list.A
[String]/[Int]/[Boolean]field can receive"",0, orfalseinstead of a one-element array. The previousasArrayhelper treated those as empty and produced[], so rename and other input transforms dropped a valid value.nullis still returned as-is. A real list is still walked item by item.inversify/monorepo (@inversifyjs/http-core)
v5.9.1Compare Source
Patch Changes
webpro-nl/knip (knip)
v6.44.0: Release 6.44.0Compare Source
entrystill adds entry files from package.json (#2206) (4099dde) - thanks @MannXo!9d8464d) - thanks @fixfon!7569702) - thanks @fixfon!d412c5b) - thanks @Cherry!d6f594c) - thanks @abrahamguo!ef5b819)54b02dd)entryin plugins that do not resolve their config files (0b0e328)38d926a) - thanks @jakeleventhal!cefef30) - thanks @jakeleventhal!cfe91ab) - thanks @jakeleventhal!611e7db) - thanks @clean99!3f35bbd) - thanks @renovate[bot]!86ab963) - thanks @clean99!51a8d33)e535f40) - thanks @jay23606!a50e842) - thanks @clean99!668aea6) - thanks @clean99!8e48df6)dd4e1f7) - thanks @ashokram-si!findPackageJSON()bare specifiers as dependencies (#2235) (d4e387b) - thanks @abrahamguo!f286584) - thanks @APX403!8d1d1d1) - thanks @gioboa!reporterin the Mocha plugin (#2232) (c413715) - thanks @X-Guardian!724c3c9) - thanks @SwastikTripathi!dde22a7) - thanks @SwastikTripathi!5e10c52) - thanks @gioboa!387e97f)98180d3)c224f16)c2598a3)c264697)b3f9a56)build.lib.entrypaths in the Vitest plugin (5d974fa)8f93e9d)testDirpaths in the Playwright plugin (4e3e6b3)storiespaths in the Storybook plugin (321decc)basePathin the Karma plugin (64e8b1b)058930d)0176d78)run-commandscwd from the workspace root (39c08aa)168ee52)7945ec1)rootfrom the repository root (f28fae6)dirinstead of absolutizing them in the webpack, Nx and textlint plugins (1ad804d)relativecalls on entry patterns in the rstest and Marko plugins (9096f25)toAbsolutein the Jasmine, Lunaria and electron-vite plugins (b4266ef)2fb1024)af469e9)efe514f)b515677)requireandfilefrom the working directory (c6850eb)jsxImportSourcein the tsconfig plugins test (0442096)nyc.config.{js,cjs,mjs}in the nyc plugin example (671e5fb)e6cbfe3)15cd870)2730ffa)dir(6df9c4e)working-directoryfixtures for mocha spec patterns (95efd3a)dir(2070464)98d0b98)cwd(381e3e3)dirin the Playwright, Railway and mise plugins (5d10668)1a58eb5) - thanks @X-Guardian!e118ef4) - thanks @gioboa!acbbbf5) - thanks @gioboa!624da93) - thanks @fixfon!153ba1e) - thanks @NgoQuocViet2001!e68eaa5)8b06f9a)v6.43.0: Release 6.43.0Compare Source
39af70a)46a825d)ba527f7)dbd3a8b) - thanks @tlq5l!@referencein Tailwind CSS compiler (#2177) (219f16d) - thanks @mkantautas!{ find, replacement }array form of Vitealias(#2179) (5d0779b) - thanks @mkantautas!100ef49) - thanks @Cayan!9cf928b) - thanks @jakeleventhal!c301e44) - thanks @abrahamguo!--fixfor exports in multi-declarator variable statements (#2178) (326afd9) - thanks @mkantautas!16d9932) - thanks @abrahamguo!references(#2186) (d741c46) - thanks @mkantautas!@pluginoptions blocks in Tailwind CSS compiler (#2187) (9fae773) - thanks @mkantautas!--fix(#2188) (6748259) - thanks @mkantautas!e971b09) - thanks @TomasHubelbauer!90216c2) - thanks @ryanquinn3!isSsrBuildto Vite config functions (#2191) (d2aa101) - thanks @mkantautas!srcof<script>and<style>blocks in Vue SFCs (#2193) (3d14839) - thanks @mkantautas!--fix(#2192) (231026c) - thanks @mkantautas!b2cc439)parserOptions.parserin ESLint flat configs (#2198) (302f908) - thanks @mkantautas!test.projectsto their config (#2195) (4d38613) - thanks @fixfon!script-*when extracting script blocks (#2199) (23e6479) - thanks @mkantautas!fc92470) - thanks @jakeleventhal!8f21ea2)6569cdc)--fixexport ranges inside a larger removal (204a809).travis.ymlwith a stat instead of a glob (3601c6e)813fa30) - thanks @mkantautas!12e4355) - thanks @mehdimirzafaruk!test.projects(#2197) (ec293d1) - thanks @mkantautas!89dfdc8) - thanks @sushanta-neupane!t,tstandrun-scriptaliases (ce91e23)vitest-environment-nuxtas optional (it comes with@nuxt/test-utils) (db9aa74)9434bf6)21c3b75)engines.nodeto follow Astro's (9d7a5e0)nodejs/node (node)
v24.22.2: 2026-10-28, Version 24.22.2 'Krypton' (LTS), @aduh95Compare Source
Commits
f8bdcd54ed] - deps: V8: backport786c1c2(Eliau Elkouby) #662493b93fd6b2b] - deps: V8: backport1a00890(Jakob Linke) #657645aaf62faaa] - deps: V8: backportc9c0abf(Jakob Linke) #657643b8eb1a920] - deps: V8: backportebd1578(Marja Hölttä) #65764ab70b5d681] - deps: V8: cherry-pick853553f(Victor Gomes) #6624117ec999f24] - stream: keep async context of parked writes (Matteo Collina) #66907pnpm/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
<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, throughprefixin `registConfiguration
📅 Schedule: (UTC)
🚦 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 has been generated by Mend Renovate CLI.