On Sun, Apr 26, 2020 at 4:33 pm, Paolo Greppi <paolo.gre...@libpf.com>
wrote:
My understanding is that node-gulp-babel v8 should be used with
babel7.
Same goes for node-babel-loader, you need v8 for babel7, but we only
have node-babel-loader 7 in Debian.
If we want babel6 to co-exist with babel7, then we don't want to just
update node-gulp-babel and node-babel-loader to v8.
We want to keep node-gulp-babel and node-babel-loader at v7 for
compatibility with babel6, and upload new node-gulp-babel8 and
node-babel-loader8 for babel7.
My suggestion,
1. node-rollup-plugin-babel: Plan A, update all packages build
depending on node-rollup-plugin-babel to build with babel 7 (psl.js
updated already and seems pretty straight forward). Plan B, embed
rollup-plugin-babel 4 in node-babel7 if plan A becomes too difficult.
2. node-gulp-babel: Plan A, update all packages build depending on
node-gulp-babel to babel 7. Plan B: embed gulp-babel 8 in node-babel 7
as it seems a simple module unlike rollup-plugin-babel.
3. babel-loader: This is not a blocker as node-babel7 build depends on
node-rollup-plugin-babel and node-gulp-babel only.
Lets use https://wiki.debian.org/Javascript/Nodejs/Transitions/Babel7
to track the status.
Back to the topic of this bug, do we really want to upgrade the yarn
build system from babel6 to babel7 ?
Here is some indication that upstream is not interested:
https://github.com/yarnpkg/yarn/pull/6322
But I have raised the issue anyway:
https://github.com/yarnpkg/yarn/issues/8083
Ideally we should have only one version of babel in bullseye and we
should try to get rid of babel 6 by bullseye freeze. Even if upstream
is not interested, we will have to maintain the patch.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
