You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're stuck into depending on an old version on strip-ansi, just because npm sucks (more info here: ca64fcd ).
The alternative to this - at least the one I can think of - is to bump up the node engine we depend on to >= 12, but I wasn't at all ready to do that (and drop support to those still not using such a recent version).
However, eventually, with that or another approach, this situation must be resolved.
The text was updated successfully, but these errors were encountered:
Not unlike what happened in ca64fcd ,
we must compensate for the deficiencies of npm.
In this case, mathjs 9.4.4 announces support only for node >= 12.
While it actually works on Node 10[1], we don't know for how long, and
so we're depending specificly on a version older than 9.4.4.
We will need to take this into account when dealing with #126 .
[1] josdejong/mathjs#2258
* lowdb has joined the #126 bandwagon: it now depends on node >=12,
but we still wish to keep supporting node 10;
* regenerating the package-lock.json file also closes#131, bumping
ansi-regex from 5.0.0 to 5.0.1.
chalk 5 is not retrocompatible (see #137).
For now we are depending on chalk <=4 to fix that, and
Nodiverse >= 0.4.1 (which also depends on chalk <= 4).
In the future we might try to support more recent versions of chalk
too, but that will mean bumping node's dependency to
`"node": "^12.20.0 || ^14.13.1 || >=16.0.0"`, and as we can see in
issue #126 we're still not ready to stop supporting node 10.
We're stuck into depending on an old version on
strip-ansi
, just becausenpm
sucks (more info here: ca64fcd ).The alternative to this - at least the one I can think of - is to bump up the node engine we depend on to >= 12, but I wasn't at all ready to do that (and drop support to those still not using such a recent version).
However, eventually, with that or another approach, this situation must be resolved.
The text was updated successfully, but these errors were encountered: