On Fri, Dec 18, 2020 at 15:08, Xavier <[email protected]> wrote:
<very approximate english>
Problems:
1 - @babel/runtime
Looking at @babel/runtime doc:
"This is meant to be used as a runtime dependency along with the
Babel
plugin @babel/plugin-transform-runtime. Please check out the
documentation in that package for usage."
If @babel/runtime is always used with @babel/plugin-transform-runtime,
then impossible to split it (see
https://people.debian.org/~yadd/babel-spaghetti-dish.png). However
@babel/runtime itself has no dependencies, so if it is useful I can
separate it, but I'd like to have confirmation.
@babel/runtime needs to be a dependency when using
@babel/plugin-transform-runtime as build dependency. so there is no
benefit in adding @babel/plugin-transform-runtime with @babel/runtime
2 - @babel/standalone
Current build doesn't really ship all needed @babel/foo (many are
considered as external dependencies during build. See
/usr/share/nodejs/@babel/standalone/index.js). So for now,
node-babel7-standalone will depends on node-babel7.
To change this, build must be modified to really provide the whole
@babel/standalone. But in this case, node-babel-standalone will be a
big
package, is there really a benefit in this split?
</very approximate english>
This is to be used in browsers as a replacement for entire babel, to
directly run ES6 code. So either we have to build the complete babel or
it is not very useful. So until we build it fully, we cannot split it.
@gitlab/ui has a dependency on @babel/standalone (though not very
urgent at this time as gitlab itself is in contrib and there is a long
way to go before it can be in main).
