severity:serious
justification: fails to build from source

While trying to rebuild reverse (build) dependencies of node-dateformat
5.0.3 just uploaded to experimental, I noticed eslint is ftbfs. Just to
confirm if that is related to node-dateformat I checked
https://tracker.debian.org/pkg/eslint and found autopkgtest is already
failing with same error.

autopkgtest log
https://ci.debian.net/data/autopkgtest/unstable/amd64/e/eslint/21361051/log.gz

not ok 386 - /<<PKGBUILDDIR>>/tests/lib/cli-engine/formatters/stylish.js
  ---
  message: '"chalk" is not found.'
  severity: error
  data:
    line: 13
    column: 21
    ruleId: node/no-missing-require
  ...

Please check compatibility with node-dateformat 5.0 once you fix the
ftbfs.

Full sbuild log attached.

Hi,

I'm unable to reproduce this issue, can someone confirm ?

Quoting Yadd (2022-06-10 10:08:54)

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.

I am leaving the bug open since it evidently existed and I have no idea
if there is still a bug somewhere - most likely elsewhere than in eslint
since it appeared and went away with *zero* changes to eslint itself!

If someone is confident that this issue is solved now, then please close
this bugreport.  Or if someone has a clue which other part of the insane
Node.js ecosystem caused this bug then please share here, and/or
reassign to that package.


 - Jonas