-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(builtin): fix for nodejs_binary entry point in bazel-out logic #1739
fix(builtin): fix for nodejs_binary entry point in bazel-out logic #1739
Conversation
ed6cbe3
to
fa0b8fb
Compare
fa0b8fb
to
ea5058f
Compare
If entry point is a generated file in bazel-out nodejs_binary fails with ``` Error: Cannot find module '/private/var/tmp/_bazel/.../foobar.sh.runfiles/wksp/bazel-out/plat-form/bin/path/to/entry_point.js' ```
ea5058f
to
6899453
Compare
@@ -191,7 +191,10 @@ for ARG in "${ALL_ARGS[@]:-}"; do | |||
case "$ARG" in | |||
--bazel_node_modules_manifest=*) MODULES_MANIFEST="${ARG#--bazel_node_modules_manifest=}" ;; | |||
--nobazel_patch_module_resolver) | |||
MAIN="TEMPLATED_script_path" | |||
declare MAIN=$(rlocation "TEMPLATED_entry_point_manifest_path") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did we never see this bug before?? We've had entry_point pointing to bazel-out for a while haven't we? or is this the first time we are trying to do that without the patched module resolver?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know. I was surprised as well. We always had main.ts as the entry point of which was renamed to main.js by the rule & the parched resolver always found it.
…logic (bazel-contrib#1739)" This reverts commit a6e29c2.
Pre-factor out of #1715
If entry point is a generated file in bazel-out nodejs_binary fails with