Change from babel+terser to swc#447
Conversation
…nifying - Only print analytics once per build - Rebuild dist and demo - Removed nodent, should no longer be necessary - Remove rollup-plugin-cleanup, minifying from swc does it
|
You can pick either this, or #445 - or none of them, but you can't pick both :-) |
|
Hello @folknor, Thanks for putting this together, and for linking it with the context in #446. I appreciate you testing the resulting build in your app as well. Moving to SWC is definitely an interesting direction. The build pipeline is one of the key areas I will be revisiting as part of the upcoming v11 release, and your work on both this and #445 will be a valuable reference for that decision. Since you know the internals well at this point, I would love to have you involved in the v11 build tooling discussion when the release plan is out. Your input would be very valuable as always. I will be publishing the v11 release plan soon, so stay connected for updates. Thanks as always for your continuous support, much appreciated! Have a nice day, cheers! :) |
2 participants
Hi
This commit contains some of the changes I talk about it #446
It changes the build to use swc instead of babel+terser, but keeps the dist/ and demo/ as a CJS instead of ESM, and keeps compatibility with es2015 (es3).
It also removes nodent, removes rollup-plugin-cleanup, rebuilds dist/ and demo/, and limits the analytics to only print once.
I've tested the resulting build in my app and it works fine there :-)
Thank you