is it still modern if its been around for 3+ years and is still not the default? I haven't looked at it since, so still no clue what it would take to support it

the trouble with this since the start has been that it isn't documented anywhere how it actually works. they just provide plugins for tools that need it, but those are written in JS and not useful for shadow-cljs. so if you have docs explaining how it works and how to use it from a non-standard build tool I'll happily take a look. shouldn't be more complicated to implement than the current npm resolve nightmare, just never found anything on how to even do that.

@thheller I wasn't advocating for adoption or integration, i'm leaning towards removing yarn because the functionality i need the most is in NPM and the direction it's going it's going (of which there are many) seems better handled by other tools given my setup. I was just curious if anyone had gone down the route of using yarn 2 or 3.