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
When trying to use a vendored version of yarn via vendored_yarn bazel doesn't include the specified folder inside the external folder of the output user root. We have tested both using a local_repository and the http_archive like the vendored_node_and_yarn example and both fail to include yarn which causes yarn commands to not work (eg: bazel run @nodejs//:yarn_node_repositories). Doing a bazel sync seems to force bazel to detect the dependency and fixes the issue, but it is not a great fix to ask every one using our repo to do it locally.
Running yarn in rules_nodejs_vendored_yarn
internal/modules/cjs/loader.js:582
throw err;
^
Error: Cannot find module 'bazel_output\wk6kt6hu\external\vendored_yarn_1_10_0\yarn-v1.10.0\bin\yarn.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
at Function.Module._load (internal/modules/cjs/loader.js:506:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
at startup (internal/bootstrap/node.js:285:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs!
🐞 bug report
Affected Rule
vendored_yarn inside node_repositories
Description
When trying to use a vendored version of yarn via vendored_yarn bazel doesn't include the specified folder inside the external folder of the output user root. We have tested both using a local_repository and the http_archive like the
vendored_node_and_yarn
example and both fail to include yarn which causes yarn commands to not work (eg:bazel run @nodejs//:yarn_node_repositories
). Doing abazel sync
seems to force bazel to detect the dependency and fixes the issue, but it is not a great fix to ask every one using our repo to do it locally.🔬 Minimal Reproduction
Using the basic workspace setup at https://github.com/ceraetes/rules_nodejs_vendored_yarn (modified version of the example to use self-managed dependencies) and trying to run
bazel run @nodejs//:yarn_node_repositories
will trigger the issue.🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_nodejs version:
(Please check that you have matching versions between WORKSPACE file and
@bazel/*
npm packages.)Anything else relevant?
The text was updated successfully, but these errors were encountered: