hm I’m thinking it’s meant to be done via bb.edn but since i’m compiling files via framework’s build process (webpack and metro), this would just be a separate step of creating bb compiled file with deps

ok seeing how nbb loads deps to see what could be done https://github.com/babashka/nbb/blob/df170a3a6bd7ec3ca009c39b207fc2f7d7dac925/src/nbb/api.cljs#L48 still wondering what the overall expectation is before going in on any one solution

yeah, there's an issue for this here: https://github.com/squint-cljs/cherry/issues/64

not yet implemented

example isn’t fully working but i did extract the logic in case anyone follows this trail https://github.com/alidcast/next-cherry-cljs-example

oh wow did not know shadow-cljs recently released an esm target https://shadow-cljs.github.io/docs/UsersGuide.html#target-esm I still see value in having cljs exposed as npm module and not depending on google closure compiler, but this does alleviate some of the pain points Cherry was resolving

I wonder how difficult it’d be for shadow-cljs to integrate a cherry-cljs target

yes, cherry of course uses shadow with the esm target to build itself, so does #C029PTWD3HR