Unify transpilation of nextcloud JS libraries about standards HOT 2 OPEN

Thoughts

From my point of view libraries should not be transpiled, only if written in Typescript (then transpiled to ES version supported by our Node version (currently ES2022)), as I would always recommend transpiling all dependencies to make sure there is no compatibility issue.

This way we could provide smaller bundles as we only need to include polyfills once in the apps and do not have them duplicated within all dependencies / libraries.
Moreover I would recommend simply using ESBuildMinifyPlugin on Apps, which is a lot faster then running babel-loader on every dependency, of cause one would need to include polyfills as well, but this can be handled by webpack-plugin-corejs.
See build time and size comparison data below.

But on a long term I would love to see nextcloud support ES6 modules as scripts, all of out target browser support ES6 natively, the only problem is nextcloud-server which does not support adding ES6 scripts (missing type="module" on script tag).
See also comparison data below why this would yield much better performance.

Build time and size comparison

from standards.

From my point of view libraries should not be transpiled, only if written in Typescript (then transpiled to ES version supported by our Node version (currently ES2022)), as I would always recommend transpiling all dependencies to make sure there is no compatibility issue.

I second that.
It will also cleanup our code and libraries boilerplate

But on a long term I would love to see nextcloud support ES6 modules as scripts, all of out target browser support ES6 natively, the only problem is nextcloud-server which does not support adding ES6 scripts (missing type="module" on script tag).

A different discussion, but seeing the table you posted, oh man, sign me up for webpack+swc already! 😱
The difference with what we do is really manageable I'd say

from standards.