[Pkg-javascript-devel] Removing babel 6: Call for help

[Pirate Praveen]

On 2020, മേയ് 18 5:34:41 PM IST, Pirate Praveen <praveen at onenetbeyond.org> wrote:
>
>
>On Sat, May 16, 2020 at 8:39 pm, Daniel Ring <dring at wolfishly.me> wrote:
>> I updated the Rainloop package on Salsa; please take a look at it, 
>> and sponsor an upload to the archive if you think it's ready.
>> 
>
>Thanks for the fix, I have uploaded it.

With rainloop also fixed, node-yarnpkg is the last blocker for babel 6 removal (libjs-webrtc and rails have fixes ready for upload).

I think babel-plugin-transform-inline-imports-commonjs is the source of the problem (from what I understood trying various babel plugins and options and their permutations and combinations). This plugin is not compatible with babel 7, but there is a fork which has updated parts of it to use babel 7, but it still uses babel-plugin-transform-strict-mode from babel 6 (when trying to use @babel/pluging-transform-strict-mode from babel 7 node-yarnpkg build fails). So one possible solution could be to update this plugin to use @babel/pluging-transform-strict-mode and then try again.

There is @babel/transform-modules-commonjs which is supposed to do the same thing in babel 7 but that does not work as documented. If we can get this plugin to work, that could also be one possible solution.

Last resort, if we can avoid the circular dependencies by patching, that could work as well. lazy loading allows circular dependency but somehow it is failing to properly transpile the lazy loading and fails with circular dependencies.

Another option is to jump to yarn 2.x branch, though it is still a release candidate. I think this would be the easiest option from a JS skill point of view, but may involve updating some dependencies and can potentially take longer.

I hope someone who has better JS skills than me can help here.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.