@pnpm/installing.linking.real-hoist 1100.1.14 → 1100.1.16

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @pnpm/real-hoist
 
+## 1100.1.16
+
+### Patch Changes
+
+- Updated dependencies:
+  - @pnpm/deps.path@1101.0.1
+  - @pnpm/lockfile.types@1100.1.0
+  - @pnpm/lockfile.utils@1102.1.0
+
+## 1100.1.15
+
+### Patch Changes
+
+- Under `nodeLinker: hoisted`, peer-resolution variants of an injected directory dependency (a `file:` snapshot) are materialized as separate copies again instead of collapsing onto the first-seen variant. Each copy keeps its own peer-resolved dependency set, so a project pinning one peer version no longer resolves another project's variant — Bit root components with conflicting peers across injected copies rely on this.
+
 ## 1100.1.14
 
 ### Patch Changes

package/lib/index.d.ts

@@ -31,6 +31,16 @@ export type { HoisterResult };
  * `(alias, depPath)`, so an alias exposing a package under a second
  * name gets a node, and a directory, of its own. An index over the
  * result holds the list and resolves an edge to its first entry.
+ *
+ * An injected directory dependency (a `directory` resolution) keeps
+ * its peer suffix: every variant of it is a separate on-disk copy of
+ * the local package, materialized with its own peer-resolved
+ * dependency set, so collapsing the variants would rewire every
+ * dependent of the losing one onto the survivor's children (Bit's
+ * root components pin conflicting peers across such copies on
+ * purpose). The registry collapse exists to stop peer-variant
+ * explosion on large lockfiles; directory snapshots are one per
+ * injected workspace package and cannot explode that way.
  */
 export declare function getHoisterPkgId(depPath: string, pkgSnapshot: PackageSnapshot): string;
 /**

package/lib/index.js

@@ -18,8 +18,25 @@ import { hoist as _hoist, HoisterDependencyKind } from '@yarnpkg/nm/hoist';
  * `(alias, depPath)`, so an alias exposing a package under a second
  * name gets a node, and a directory, of its own. An index over the
  * result holds the list and resolves an edge to its first entry.
+ *
+ * An injected directory dependency (a `directory` resolution) keeps
+ * its peer suffix: every variant of it is a separate on-disk copy of
+ * the local package, materialized with its own peer-resolved
+ * dependency set, so collapsing the variants would rewire every
+ * dependent of the losing one onto the survivor's children (Bit's
+ * root components pin conflicting peers across such copies on
+ * purpose). The registry collapse exists to stop peer-variant
+ * explosion on large lockfiles; directory snapshots are one per
+ * injected workspace package and cannot explode that way.
  */
 export function getHoisterPkgId(depPath, pkgSnapshot) {
+    // `resolution` is typed as required, but the lockfile is parsed from
+    // untyped YAML — guard so a malformed snapshot degrades to the
+    // collapsed identity instead of a TypeError here.
+    const resolution = pkgSnapshot.resolution;
+    if (resolution != null && 'directory' in resolution && resolution.directory != null) {
+        return depPath;
+    }
     const { name, version } = nameVerFromPkgSnapshot(depPath, pkgSnapshot);
     return `${name}@${version}`;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnpm/installing.linking.real-hoist",
-  "version": "1100.1.14",
+  "version": "1100.1.16",
   "description": "Hoists dependencies in a node_modules created by pnpm",
   "keywords": [
     "pnpm",
@@ -27,18 +27,18 @@
     "!*.map"
   ],
   "dependencies": {
-    "@pnpm/deps.path": "1101.0.0",
+    "@pnpm/deps.path": "1101.0.1",
     "@pnpm/error": "1100.1.3",
-    "@pnpm/lockfile.types": "1100.0.20",
-    "@pnpm/lockfile.utils": "1102.0.0",
+    "@pnpm/lockfile.types": "1100.1.0",
+    "@pnpm/lockfile.utils": "1102.1.0",
     "@yarnpkg/nm": "4.1.1"
   },
   "devDependencies": {
     "@jest/globals": "30.4.1",
-    "@pnpm/installing.linking.real-hoist": "1100.1.14",
-    "@pnpm/lockfile.fs": "1100.2.3",
+    "@pnpm/installing.linking.real-hoist": "1100.1.16",
+    "@pnpm/lockfile.fs": "1100.2.5",
     "@pnpm/test-fixtures": "1100.0.1",
-    "@pnpm/types": "1102.0.0"
+    "@pnpm/types": "1102.1.0"
   },
   "engines": {
     "node": ">=22.13"