David

I want to add here that sharding is working the way I have it setup. But I will leave this open as it may be useful to have for others....

We use `playwright` directly through `rules_js` since it provides a test target via the exported bin. Then we have been modifying that on our own to support our needs. Just...

You will need to explore aspect-cli and gazelle to do build file generation, which is what I think you are asking

That is not what I was referring to, that's an alternative solution though. I was referring to https://github.com/aspect-build/aspect-cli/tree/main/gazelle/js If you plan on using the Aspect solutions, probably best to reach...

Looks like https://github.com/aspect-build/rules_js/blob/main/npm/private/npm_translate_lock_helpers.bzl#L10-L48 fails to check the case if there is an input on a hosted package, but there is no found result in the array

In our case (I was looking through our lockfile) peer dependencies are not ending up encoded in the leaf package. Dev Dependencies are. A common pattern in the JS ecosystem...

One thing I wanted to add to this is that we set the `rootDir` of `jest` to be the bazel target directory instead of the root of the bazel workspace....

What's the thought process behind treating these things as different? Seems confusing for packages that are depended on by multiple targets to be considered a `js_library` instead of an `npm_package`...

Also one other thought on this that our company will hit if everything ends up in `dependencies` it makes tools like `Snyk` assume things are getting shipped to prod. While...

Here is the line in ibazel that is throwing https://github.com/bazelbuild/bazel-watcher/blob/master/internal/bazel/bazel.go#L292