fix(builtin): correctly calculate pkg._directDependency when a mapped node_module is used

Author: mistic

internal/npm_install/generate_build_file.ts

@@ -661,7 +661,7 @@ export function parsePackage(p: string, dependencies: Set<string> = new Set()):
 
   // set if this is a direct dependency of the root package.json file
   // which is later used to determine the generated rules visibility
-  pkg._directDependency = dependencies.has(pkg._moduleName) || dependencies.has(pkg._name);
+  pkg._directDependency = dependencies.has(pkg._moduleName) || dependencies.has(pkg._name) || dependencies.has(pkg._dir);
 
   return pkg;
 }

internal/npm_install/index.js

@@ -387,7 +387,7 @@ function parsePackage(p, dependencies = new Set()) {
     pkg._files = listFiles(p);
     pkg._runfiles = pkg._files.filter((f) => !/[^\x21-\x7E]/.test(f));
     pkg._dependencies = [];
-    pkg._directDependency = dependencies.has(pkg._moduleName) || dependencies.has(pkg._name);
+    pkg._directDependency = dependencies.has(pkg._moduleName) || dependencies.has(pkg._name) || dependencies.has(pkg._dir);
     return pkg;
 }
 exports.parsePackage = parsePackage;