Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1019369 > unrolled thread

Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined Adrian Bunk <bunk@debian.org> - 2020-07-26 18:40 +0200
    Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined Pirate Praveen <praveen@onenetbeyond.org> - 2020-07-26 19:20 +0200
    Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined Xavier <yadd@debian.org> - 2020-07-27 07:30 +0200

#1019369 — Bug#965353: [Pkg-javascript-devel] Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined

On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
> I'm wondering if this will require another bootstraping cycle as node-babel7
> autopkgtest is also broken and it depends on itself.

If the problem is in node-lodash and gets fixed there,
shouldn't this fix everything?

cu
Adrian

[toc] | [next] | [standalone]

#1019376 — Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined

On Sun, Jul 26, 2020 at 22:24, Pirate Praveen 
<praveen@onenetbeyond.org> wrote:
> Babel build situation is indeed a mess.

It is even worse than I estimated. We can no longer build it with npm

DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild
...

HOME=`pwd` npm i
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "link:": 
link:./eslint/babel-eslint-config-internal

we have to change it to yarn.

[toc] | [prev] | [next] | [standalone]

#1019429 — Bug#965353: [Pkg-javascript-devel] Bug#965353: Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined

Le 26/07/2020 à 18:54, Pirate Praveen a écrit :
> 
> 
> On Sun, Jul 26, 2020 at 19:35, Adrian Bunk <bunk@debian.org> wrote:
>> On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
>>>  I'm wondering if this will require another bootstraping cycle as
>>> node-babel7
>>>  autopkgtest is also broken and it depends on itself.
>>
>> If the problem is in node-lodash and gets fixed there,
>> shouldn't this fix everything?
> 
> I don't think the problem is in lodash as I can see babel upstream is
> already using lodash 4.17.19 in their yarn.lock
> https://github.com/babel/babel/blob/f7964a9ac51356f7df6404a25b27ba1cffba1ba7/yarn.lock#L7114

Hi,

our lodash build does not provide the same result than npm package.

> I think babel needs to use the same version of lodash it was built with
> and a breaking change in lodash was released as a minor/patch
> release/security release.
> 
> I think it is becoming more and more common to break API during security
> releases (we had to face this in rack/rails in ruby team).
> 
> Babel build situation is indeed a mess.

the problem is in lodash.

> They are dicussing removing lodash from babel though see
> https://github.com/babel/babel/pull/11789

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web