Closed henrythasler closed 2 years ago
Do I need to continue to provide the other (esm, non-minified) files? Let me know your opinion.
I'd suggest keeping everything as it is. Who knows what might come in handy?
By the way, it'd be great to add command like build:debug
that'll build unminified UMD file for testing in browser. This will reduce compilation time. Caching also will help.
How can I properly test these generated files?
You're not using any polyfills, browser-specific hacks or stuff like that. Basically, you get what you write, no need for other tests.
Jest should internally compile TS to JS, unless it uses deno, so your bundle is already tested.
Thanks for the feedback. I just cleaned up the build-scripts a bit (now platform independent) but left the resulting artifacts untouched. There is now also a build:dev
command you could adapt for your purposes.
Cool, thanks!
The build pipeline currently generates these files:
The CDN statistics show that almost all downloads are just the
umd.min.js
-file:Questions: