Fix: Add implicit self-dependencies to node-modules package maps

cursoragent · cursoragent · commit ba99b5b7262e · 2026-06-15T21:49:47.000Z
When nodeExperimentalPackageMap is enabled, packages that rely on a self
symlink can now correctly resolve their own name under standard enforcement.

The node-modules package map builder now adds an implicit self-dependency
for non-workspace packages when there's no explicit self-dependency,
mirroring the behavior of the pnpm linker. This ensures parity between
both linkers' package map generation within the same PR.
diff --git a/packages/zpm/src/linker/package_map.rs b/packages/zpm/src/linker/package_map.rs
@@ -267,9 +267,16 @@ fn get_package_dependency_names(project: &Project, install: &Install, locator: &
     let tree
         = &install.install_state.resolution_tree;
 
-    resolution_dependency_names(tree, locator)
+    let mut dependency_names = resolution_dependency_names(tree, locator)
         .or_else(|| workspace_link_dependency_names(project, tree, locator))
-        .unwrap_or_default()
+        .unwrap_or_default();
+
+    // Add implicit self-dependency for non-workspace packages when there's no explicit self-dependency
+    if !locator.reference.is_workspace_reference() && !dependency_names.contains(locator.ident.as_str()) {
+        dependency_names.insert(locator.ident.as_str().to_string());
+    }
+
+    dependency_names
 }
 
 fn resolution_dependency_names(tree: &ResolutionTree, locator: &Locator) -> Option<BTreeSet<String>> {
