David

Can a fix be added to not opt people into this change by default? We have users that use `yarn` in a monorepo and those packages are not yet part...

Sorry, but that's not scalable nor an acceptable answer for an entire engineering org to adopt just to revert back to functionality that we had yesterday. It's nice there is...

Yeah that's the solution we came to also sadly

@arcanis in our case it's because we are mid migration from Yarn to PNPM and for the PNPM world we care about it being respected. Anything that's yarn based is...

The other workaround we do have is to set the .yarn/release folder with a pinned version of yarn for all projects that need to avoid this problem for now.

More for posterity but I'm chiming in here to note this is still an issue as of SWC 1.6.6. We came across it when trying to explore using webpack aliases...

My company would benefit from support for this. We currently have patched the gazelle plugin to enable this internally

Just to follow up here, the additional benefit to this would be allowing more than one test target type so we could have macros for say `jest`, `playwright`, or other...

Same as https://github.com/aspect-build/aspect-cli/issues/563, I'd expect I can do `map_kind` on this so I can provide my internal macro for jest_test that has some nice things already setup for the end...

As a user, some notes: 1. I would expect I could use gazelle to generate any npm package that rules_js produces this way 2. I would expect that I can...