Le 18/12/2020 à 14:51, Xavier a écrit : > Le 18/12/2020 à 13:44, Pirate Praveen a écrit : >> Package: node-babel7 >> Version: 7.12.11+~cs150.141.84-1 >> Severity: wishlist >> >> @babel/runtime and @babel/standalone is targetted at browsers and used >> as runtime dependencies unlike the rest of babel (all others are used as >> build dependencies). >> >> So consider creating node-babel-runtime and node-babel-standalone as >> separate binary packages. >> >> For example, now yarnpkg pulls in entire node-babel7 even though it >> needs only @babel/runtime. > > Proposition: > * node-babel7-runtime + Provides: node-babel-runtime > * node-babel7-standalone + Provides: node-babel-standalone > * node-babel7 (+ Provides the rest) > > This avoid name conflicts
<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. 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>
