Le 26/07/2020 à 18:54, Pirate Praveen a écrit : > > > On Sun, Jul 26, 2020 at 19:35, Adrian Bunk <b...@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
