squint is intended to be used for when CLJS is a bit too heavy and the majority of your code is JS interop anyway. Also if you want to publish libraries to the NPM ecosystem, squint offers lower overhead. It's not intended as a full replacement for normal CLJS

I understand that but whenever i can't use some npm i am just looking for a goog compiler alternative. And I don't know how good js tools are now compared to goog compiler advenced mode. would the size of output be significantly different . I know it is wishful thinking ...

what do you mean with "can't use some npm"?

IMHO all npms are not just usable in shadow-cljs. I tried a couple of markup npms and was not able to import them, Ok, I could be my fault. But usually i try all documented ways to require something from npm.

That may be a ESM vs CJS issue?

What kind of error did you get?

it was ESM problem

in shadow-cljs you can use :target :esm

and then you should be able to require ESM modules

squint itself is built this way

Thanks, I didn't know that

You would almost certainly get the problem solved if you post on #C6N245JGG.

if you use shadow's :target :esm, the imports should work exactly the same in nbb and squint/cherry (due to everything being ESM modules)