@thheller I think Closure has some polyfill support, does shadow do allow me to polyfill e.g. Promise?

would it just be a matter of seting the output language to :es3for example?

yes, but use :output-feature-set. the :language-out is sort of deprecated. https://shadow-cljs.github.io/docs/UsersGuide.html#_output_language_options

ah

thanks

but currently if you use js/Promise from CLJS it won't be polyfilled in development

only in release

that’s fine

what’s the default for output-feature-set?

:es5

should that polyfill Promise?

because it wasn’t working in IE11

I think promises are es5? not actually sure

oh > ES5 did not have promises.

from https://stackoverflow.com/questions/38424517/es5-vs-es6-promises

so it isn’t polyfilling when it should?

or maybe it doesn’t by default?

https://www.ecma-international.org/ecma-262/6.0/#sec-promise-objects

ECMAScript® 2015 was that es5 or es6? naming is confusing 😛

that’s es6

you may need to set :compiler-options {:rewrite-polyfills true}

I can never remember if thats on by default or not

ah

@souenzzo @mdhaney 2.8.11 fixes the goog.loader issue on react-native and it should now load properly without errors. can't actually use it due to metro but at least it won't break when loading.

@thheller do you maintain a changelog for shadow?

the changelog in the repo was last updated a year ago 😜

also, would shadow.loader.init work for the CDN use case I mentioned?

@anmonteiro yes that was the intent. set :module-loader-init false in the config an manually call shadow.loader.init(""), so only the prefix

cool

trying that right now

but I'm not too happy with that API so it may change

kk

if you could let me know I’d appreciate it

either here or tag me on a PR or commit?

if you remember

will try

thx

changelog kinda died. still need to set something up that generates that automatically

right now @jiyinyiyong kindly generates the release info for https://github.com/thheller/shadow-cljs/releases which is kinda nice

oh cool

will check that out