Greg Magolan

I'll leave it open for visibility although we have no plans to address complex and expensive rules_js Windows issues at the moment since we don't use Windows ourselves for development...

🚀 That is a long list of commits :)

I think it's too soon for all of the examples in this repo. https://github.com/bazelbuild/bazel/issues/17289 will break them all.

@vpanta Anything in here you would like to land?

I'm working on improving and generalizing this example presently so you should see some updates next week including a working devserver for development mode. The `next_entry.js` is an unfortunate work-around...

The `copy_to_bin` is a rule that copies a source file to the bazel output tree. rules_js and its derivate rules such as rules_ts always copy source files to the output...

This is generalizing into a next() macro and adding a devserver that works with ibazel: https://github.com/aspect-build/bazel-examples/pull/121

You could use [pnpm workspaces](https://pnpm.io/workspaces) which rules_js support. We have a contrived example here: https://github.com/aspect-build/rules_js/tree/main/e2e/pnpm_workspace of how it is wired up with Bazel.

Yes, we want to write our own browser toolchain at some point but we have no immediate plans to do it

How much memory does the machine have to work with and how many typescript files do you have in your repository? Using swc as the transpiler creates one target per...