Greg Magolan

This came up in the context of a question on Bazel Slack: https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1715513010992479?thread_ts=1715434089.351019&cid=CEZUUKQ6P. "sporadically" is strange and interesting. Did you have `--nobuild_runfiles_links` set when you saw this @matthewjh?

+1. This would be useful.

The desired API in your example above is nice but its not currently possible since the pnpm-lock.yaml file only says that bins exist and not what the bins are. This...

We had an old FR to pnpm to do this but the pnpm team preferred not to include the list of bins in the lock file: https://github.com/pnpm/pnpm/issues/5131

The shape of the `node_modules` in rules_js is that it is made up of output artifacts that are generated by build targets. This is why `npm_link_all_packages()` is used as under...

With Bazel I don't think that is the right shape as it is canonical to have fetches of 3p deps be lazy. If you're in a large monorepo, for example,...

For reference, there is some discussion on this feature and how to implement it in Bazel Slack here https://bazelbuild.slack.com/archives/CEZUUKQ6P/p1670931838633139

Related to https://github.com/evanw/esbuild/issues/789

Hmm. Why does `bazel build //:format` require a cc toolchain?? ``` Auto-Configuration Error: Cannot find gcc or CC; either correct your path or set the CC environment variable (02:42:38) ERROR:...

It looks like your starting point in your repro was https://github.com/aspect-build/bazel-examples/tree/main/next.js but its on an out-of-date rules_js, rules_ts & rules_swc version. Could you please try using the latest https://github.com/aspect-build/bazel-examples/tree/main/next.js was...