Alex Eagle
Alex Eagle
@ewhauser is this something you're interested in pairing with Fabian on?
Actually it seems that the performance fix is not to embed node_modules in the runfiles at all ("static linked") but include them in the execution of the program ("dynamic linked").
The resolution here is going to be using runfiles for its intended purpose, but represent node modules as TreeArtifacts.
The concatjs package is in "maintenance mode" so I don't think anyone is going to fix this.
hmm, interesting. I think we had to vendor the runfiles.bash because of a different need to patch it, @gregmagolan made these changes: https://github.com/bazelbuild/rules_nodejs/commits/stable/third_party/github.com/bazelbuild/bazel/tools/bash/runfiles Obviously you can workaround by applying that...
aspect-build/rules_webpack has an ibazel-aware devserver. Otherwise yeah it's a missing feature in general, I think big companies are rolling their own.
How is this different from `ts_project`? It already generates only one action, has a tremendously simpler implementation, and you can use the `out_dir` attribute to get different output flavors to...
@mrmeku has started a new effort for a dedicated webpack rule
Note, one possible "escape hatch" is to use plain tsc rather than ts_library, see https://github.com/bazelbuild/rules_nodejs/blob/master/packages/typescript/docs/install.md#alternatives
also worth noting what other rulesets do regarding default monorepo pathing