How to tackle a NPM dependency problem with shadow-cljs?

Being an npm user I already accept that APIs would probably breaking change in APIs if major version is bumped.

I’m also a maintainer of tens of small packages. Some of the packages are somehow experimental and I would break APIs anyway. And there are lots of packages like that in npm world. If there’s a problem, I would say the problem is npm ecosystem enabled too many junior programmers to share their own tiny(too tiny) packages that are not so stable.