Fabian Wiles

@alexeagle yeah that would be awesome if you got the time

@tristanz I think the idea here is that you don't isntall your sub packages with a `yarn install` you just reference their outputs directly

I've made a issue here #3277 to discuss ESM support in rules_nodejs - with support added it would fix this issue

Yes that's the issue we have. We'd like to only build the targets that we actually use, `.create` and `.update`

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost...

So for our repository we use `jasmine_node_test` for all our unit testing, this includes both nodejs and browser targets. Might be worth making it configurable?

@thesayyn Those node layers are meant to point to the platform specific ones, they're only aliases. If they don't work correctly then I think it's an issue with rules_nodejs not...

The size issue isn't just for slow networks, there's many other places where this would cause a regression: - The disk storage size on repositories, most notibly private repositories. -...

I tried at one stage to run Angular unit tests with on nodejs with jasmine and domino, but didn't managed to get it running. https://repl.it/@Toxicable/angular-jasmine-nodejs

@ashi009 I've done a small prototype here https://github.com/bazelbuild/rules_nodejs/pull/1856 and you're right it makes the implementation of the rules in this repository simple. However there are still a few issues im...