Update of async has broken istanbul - what is the best way forward?
Hi!
I just updated node-async to 3.2.6 (it's a dependency of something I'm
trying to package, and it also seems that those few packages that
depend on node-async all either specify async 3.x in their
package.json or don't mention async at all). Unfortunately, it's
causing the node-istanbul autopkgtests to fail. I just took at look
at the istanbul repository on GitHub, and the last update was 8 years
ago - the repository is essentially archived, but they direct to a
replacement project, IstanbulJS, which is under active development.
It also seems that the failing istanbul tests are somehow related to
nodeunit, which is also old and deprecated.
What to do now, then? Here are two possibilities:
(1) Replace the node-istanbul package with the new nyc package and the
istanbuljs packages. This would be the best thing to do, and it seems
to be only a moderate amount of work to do: almost all of the
dependencies are currently packaged (many in the current node-istanbul
source package itself). However, there may be a whole bunch of
autopkgtest failures in packages that use istanbul for testing if
istanbul/nyc is upgraded. (For a start, there doesn't appear to be an
"istanbul" executable in the current version, though I don't know how
many packages use that directly rather than nyc.)
(2) Leave the node-istanbul package at its current ancient upstream
version, but skip the failing tests. When updating the package,
though, all the autopkgtests of the depending packages will be rerun,
and some of them may fail. But hopefully it won't be too dramatic.
Hmmm.
Obviously, option (1) is the preferable option, but I don't have the
capacity (or probably the expertise) to do it; I certainly don't have
the time to chase down all the resulting test failures if I were to
upgrade it to the new IstanbulJS. So my suggestion is that I try
option (2) for now.
Any thoughts, suggestions, or offers of help before I embark on option
(2)?
Best wishes,
Julian
Reply to: