Jason Bedard

^ nope, I don't think `link:` works either...?

@gregjacobs I think you might have to just put those into the root package.json and not specify them in each workspace package. Each workspace package will still specify the fine...

I think it can be closed with pnpm workspaces as the common solution. https://github.com/aspect-build/rules_js/pull/818 will also help when depending on 3rd-party packages (without having to repeat them in every package.json...

> I see, makes sense but, explicitly setting root_dir just appends to the generated rootDir instead of replacing it The `ts_project(root_dir)` gets appended to the directory of the `ts_project` rule...

rules_ts passes the `--rootDir` cli arg 100% of the time so the `tsconfig.json` `rootDir` and default inferred path will never be used. The `ts_project(root_dir)` is relative to the BUILD its...

I don't think this is still applicable for rules_nodejs since the `run_node` call no longer exists in this repo. This is being considered as opt-in in [rules_js](https://github.com/aspect-build/rules_js) (https://github.com/aspect-build/rules_js/issues/1303) and has...

Any updates here @smacker?

We've done that for now: https://github.com/aspect-forks/go-tree-sitter/

Want to open a PR to add that to `bazel-examples`? I think I'd want to change and simplify a few things if you're open for feedback before merging it..?

Is this actually tested on CI atm? I only see oci_(go,java)...