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 using rules_js for JS projects, NPM packages are modeled as TreeArtifacts. This helps with analysis phase performance, but actions still have high overhead because TreeArtifacts are expanded, even with --noenable_runfiles.
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Description of the bug:
When using
rules_js
for JS projects, NPM packages are modeled as TreeArtifacts. This helps with analysis phase performance, but actions still have high overhead because TreeArtifacts are expanded, even with--noenable_runfiles
.Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
https://github.com/DavidZbarsky-at/nodejs-repro shows a typical JS target using node_modules, as well as reproduces the slowness directly with simple TreeArtifacts of various sizes
Which operating system are you running Bazel on?
OSX
What is the output of
bazel info release
?release 7.0.0-pre.20231011.2
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
From a long time ago :) See #5971 (comment)
Have you found anything relevant by searching the web?
#8230
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: