[Pkg-javascript-devel] Bug#1010887: eslint FTBFS and autopkgtest failure

[Yadd]

On 10/06/2022 11:07, Jonas Smedegaard wrote:
> Control: tags -1 +unreproducible
> Control: severity -1 minor
> 
> Quoting Yadd (2022-06-10 10:08:54)
>> Hi,
>>
>> I'm unable to reproduce this issue, can someone confirm ?
> 
> Yeah, I also cannot reproduce that specific failure now, so evidently
> the error was somewhere else.
> 
> A month ago I tried to work around this bug by ripping out support for
> that optional renderer altogether, only to realize *after* fighting it
> for some time that it was instead failing with some errors indicating
> incompatibility with the newer release of Node.js.
> 
> I chose to simply let it bitrot for some time to see if that _too_ was
> an error somewhere else, and apparently it was: When I try build now,
> only (yet another) single test fails, unrelated to both Node.js and
> chalk module.
> 
> I am sick and tired of the messy Node.js ecosystem.

Yes, the transition from CJS-only to the current mix generated a lot of 
work. Hope the situation will be more stable now.

I wrote some utilities to debug, part in pkg-js-tools, part in 
https://salsa.debian.org/yadd/yadd-js-tools (not well documented...).

Currently, I use porterboxes (after breaking 2 laptops...) with some 
custom tools for complex bugs:
  * first launch build until failure
  * then install wanted dependencies (first using pkgjs-install, then
    if it fails using npm/yarn --ignore-scripts)
  * retest command that failed
  * if succeed now, launch "reduce-nodejs". This tool will try to remove
    each module in node_modules, link Debian dependencies,...
  * wait a long time and do something else
  * when finish, relaunch "reduce-nodejs" to see if things can be
    improved
  * take a look at the result (version mismatch, missing modules,...) and
    try to understand the real problem

This is the better way I found to be able to update jest, babel,...

Cheers,
Yadd