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
fix: allow js_run_binary to hoist runfiles in the exec configuration
The `js_run_binary` macro has a `use_execroot_entry_point` option which is
enabled by default and which hoists out the runfiles into the execroot.
Currently this hoisting effectively rebuilds the runfiles in the target
platform config, but they should really be in the exec config since they
consist of code that is going to run during the build action.
This change fixes that problem by making sure we hoist the runfiles in the exec
config. I also updated the launcher script, since it needs to be prepared to
look for the entry point in a different directory. This is all guarded by the
`hoist_runfiles_to_exec_cfg` option on `js_run_binary`, which effectively
defaults to False for now. The default is actually `None` but only for
technical reasons.
The default is controlled by a new flag `//js:_hoist_runfiles_to_exec_cfg`, but
this is intended only for our own CI purposes, allowing us to run most tests
against both behaviors. There are a handful of `js_run_binary` targets that
require one behavior or the other, so I updated those ones to explicitly
specify the flag they need.
This addresses #2754, #2121, and #2073, but does not automatically fix them yet
since the fix is opt-in for now.
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
0 commit comments