Fixes #1092.

This PR adds the ability to link js_library targets at 1p deps in addition to npm_package targets. Using js_library to link results in a symlink into the js_library package directory in the output tree instead of a copy_to_directory of the npm_package TreeArtifact. This more closely matches how pnpm handles 1p linked deps and it fixes the long standing bug with 1p peer deps reported in #1092.

The new test case //examples/npm_deps:test9 illustrates how the //examples/npm_package/packages/pkg_d:pkg_d js_library that is linked examples/npm_deps/package.json as a "@mycorp/pkg-d": "workspace:*" 1p npm package in the pnpm lock file.

bazel-bin/examples/npm_deps/node_modules/@mycorp/pkg-d -> ../../../../node_modules/.aspect_rules_js/@mycorp+pkg-d@0.0.0/node_modules/@mycorp/pkg-d

bazel-bin/node_modules/.aspect_rules_js/@mycorp+pkg-d@0.0.0/node_modules/@mycorp/pkg-d -> ../../../../../examples/npm_package/packages/pkg_d

This is one extra level of indirection vs. what pnpm does but the result is the same in that the npm package 1p symlink examples/npm_deps/node_modules/@mycorp/pkg-d can be resolved back to the output-tree package of the js_library target examples/npm_package/packages/pkg_d. In pnpm, the symlinks goes directly there and not through the package store and, of course, it points into the source tree since there is no concept of an bazel output tree outside of bazel. Under rules_js the extra level of indirection fits nicer into the current support for npm_package and so makes for simpler code to support both modes.

Type of change

• New feature or functionality (change which adds functionality)

Test plan

• New test cases added