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.

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

Paolo

-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to