@john 2.19.9 should respect the push-state headers properly

Does this work with tree-shaking? Is there a chance that some functions are used, but not seen by webpack?

Since it only provides a require statement.

not currently no

in theory its possible to generate precise import that should be tree-shakable but its a lot of work

So this ALL will refer everything

ALL is just a variable name and means nothing

webpack tree-shaking just works off import and not require

If some libraries are designed with tree-shaking, parts of code will be missed with this method?

tree-shaking will not work at all, nothing will be eliminated. webpack just can't

Hmmm

Does shadow-cljs handle the polyfills? like buffer in browser

shadow-cljs also doesn't tree-shake any npm dependencies, so the end result is the same regardless of what you use

it does polyfill when it processes npm packages yes, not when using :js-provider :external

Ah, I see. What does the pollyfill actually do? Let's say I need buffer in browser, without :js-provider :external, it works with buffer in dependencies. But when I switch to :js-provider :external, Buffer is not defined.

So I have to do something?

:external means shadow-cljs doesn't process ANY npm packages. whatever you use to process the :external-index (eg. webpack) will do that instead

and newer webpack no longer provides those polyfills by default

so you need to configure webpack to provide it

yep, I knew webpack5 doesn't provide it

Oh, I see

Thank you!

Now, it works to me

JavaScript is so complex