Closed skagedal closed 3 months ago
Going through npm why inflight
, these seem to be the top-level dependencies where it enters mocha
:
❯ npm why inflight | grep "root project" | awk '{$1=$1};1' | sort | uniq
dev @11ty/eleventy@"^1.0.0" from the root project
dev @rollup/plugin-commonjs@"^21.0.2" from the root project
dev @rollup/plugin-multi-entry@"^4.0.1" from the root project
dev assetgraph-builder@"^9.0.0" from the root project
dev canvas@"^2.11.2" from the root project
dev eslint@"^8.56.0" from the root project
dev hyperlink@"^5.0.4" from the root project
dev karma-mocha-reporter@"^2.2.5" from the root project
dev karma-sauce-launcher@"^4.3.6" from the root project
dev karma@"^6.4.2" from the root project
dev markdownlint-cli@"^0.30.0" from the root project
dev nyc@"^15.1.0" from the root project
dev rimraf@"^3.0.2" from the root project
glob@"8.1.0" from the root project
(adding links to other issues here)
Yeah, this comes in as a dependency of glob
. Moving to a newer version is tracked in #5148. Thanks for filing!
As noted in this eslint issue,
mocha
has a transitive dependency to the deprecated, memory-leaking inflight package.This is not a direct dependency of mocha, but comes in through several paths.
For some reason, I don't get the deprecation warning when I run npm install --ignore-scripts from current main (commit
2f3fedcc
):However, the deprecated module
inflight
does get installed intonode_modules
. This issue exist to track its removal through various dependencies.