Open mcollina opened 2 months ago
As are 95 million other people every week, nearly as many as are using the latest, v4: https://majors.nullvoxpopuli.com/q?minors=&old=&packages=debug
node may want to reconsider this deprecation given the usage.
Additionally, motivated by recent CITGM failures, tape's tests should no longer be failing due to these debug messages: 8d40837
@ljharb that's not released yet.
ah, i thought CITGM was configured to run on tape's HEAD instead of the latest version.
Unfortunately I can't upgrade beyond debug v2 due to engines constraints. If this API is indeed something node is determined to remove, it'd be ideal to ship a backport in debug that refactors to avoid using it.
~Largely it does not seem feasible, because the v2 line of debug is already patched. This is due to some dependencies using locked versions.~
We'll revert in Node
Makes sense. Which dependencies are using locked versions? I could certainly see about updating those, so node isn't held back.
nyc
depends on debug@2
, which does not have the patch.
aha, gotcha. there remains one ecosystem-active maintainer of debug; i can try to pursue a backport?
I think it would be best. nyc will keep the noisy warning anyway for another semver-major cycle of Node.js.
The warning can't be removed as a non-major?
Currently using util._extend()
emits a warning. In v23, this will have the same behavior of v22.
We will remove it at some point.
Currently the tests for tape fails on Node v23:
I think this is using an old version of
debug