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
We have a number of npm dependencies that rely on the lifecycle scripts to build themselves using gyp. Instead of using gyp, we would like to build these packages using our own hermetic cc toolchain in Bazel. It would be great if there is a way to substitute a package in npm_translate_lock with a Bazel target.
Example hypothetical API to substitude node-re2 npm dependency with @node-re2 target:
What is the current behavior?
No response
Describe the feature
We have a number of npm dependencies that rely on the lifecycle scripts to build themselves using gyp. Instead of using gyp, we would like to build these packages using our own hermetic cc toolchain in Bazel. It would be great if there is a way to substitute a package in
npm_translate_lock
with a Bazel target.Example hypothetical API to substitude
node-re2
npm dependency with@node-re2
target:The text was updated successfully, but these errors were encountered: