Open anomiex opened 1 month ago
Same warning on my dependency tree:
├─┬ jest@29.7.0
│ └─┬ @jest/core@29.7.0
│ ├─┬ @jest/reporters@29.7.0
│ │ └── glob@7.2.3
│ ├─┬ jest-config@29.7.0
│ │ └── glob@7.2.3
│ └─┬ jest-runtime@29.7.0
│ └── glob@7.2.3
├─┬ ts-jest@29.2.4
│ └─┬ @jest/transform@29.7.0
│ └─┬ babel-plugin-istanbul@6.1.1
│ └─┬ test-exclude@6.0.0
│ └── glob@7.2.3
Should switch to glob@10.4.2
Duplicate of https://github.com/jestjs/jest/issues/15173 ? (maybe not exactly)
Not necessarily. #15173 is reporting the warnings in 29.7.0, which were partially fixed by #14509. Same for #15087. This issue is specifically about what remains in 30.0.0-alpha.5 after #14509.
Unfortunately test-exclude
has dropped Node 16, so we cannot upgrade in the babel plugin. Might be able to drop the dep, tho?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
Issue still exists in jest@next
, stale-bot.
+1
Version
30.0.0-alpha.5
Steps to reproduce
Starting with an empty project, do the following:
npm install jest@next
Expected behavior
No deprecation warnings.
Actual behavior
Additional context
The dependencies come in via
babel-plugin-istanbul
. See istanbuljs/babel-plugin-istanbul#294 and istanbuljs/babel-plugin-istanbul#295.Note this is not the same as the direct dependencies fixed by #14509.
Environment