[Bug]: npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it.

[anomiex]

Version

30.0.0-alpha.5

Steps to reproduce

Starting with an empty project, do the following:

1. npm install jest@next

Expected behavior

No deprecation warnings.

Actual behavior

npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

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

System:
    OS: Linux 6.9 Debian GNU/Linux trixie/sid
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  Binaries:
    Node: 20.16.0 - /usr/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.8.1 - /usr/bin/npm
    pnpm: 9.6.0 - /usr/local/bin/pnpm
  npmPackages:
    jest: ^30.0.0-alpha.5 => 30.0.0-alpha.5

[xavierraffin]

Same warning on my dependency tree:

├─┬ [email protected]
│ └─┬ @jest/[email protected]
│   ├─┬ @jest/[email protected]
│   │ └── [email protected]
│   ├─┬ [email protected]
│   │ └── [email protected]
│   └─┬ [email protected]
│     └── [email protected]
├─┬ [email protected]
│ └─┬ @jest/[email protected]
│   └─┬ [email protected]
│     └─┬ [email protected]
│       └── [email protected]

Should switch to [email protected]

[xavierraffin]

Duplicate of #15173 ? (maybe not exactly)

[anomiex]

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.

[SimenB]

Unfortunately test-exclude has dropped Node 16, so we cannot upgrade in the babel plugin. Might be able to drop the dep, tho?

[github-actions]

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.

[anomiex]

Issue still exists in jest@next, stale-bot.

[avifenesh]

+1

[EnigmaSaikat]

Quote reply

For inflight not sure for globe (v9 is available and installed manually)

for glob 9

[soderlundf]

+1

[github-actions]

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.

[anomiex]

Issue still exists in jest@next, stale-bot.

[dushmanta05]

Same issue here, is anyone working on this?

[mhanxchu]

Are there any workaround or alternatives for this?

[anomiex]

As a workaround for this specific issue in jest@next, you could use package manager overrides to use test-exclude v7 in place of the test-exclude v6 that babel-plugin-istanbul depends on. At a quick glance, I see no functional differences between 6.0.0 and 7.0.0, just the updated dependencies (which all still appear to support node 16, FWIW, despite istanbuljs/test-exclude@ad7dfe1 suggesting that deps were the reason for test-exclude requiring node >=18 rather than >=16, which is what is blocking jest and babel-plugin-istanbul from updating to that version officially).

Let's keep this issue focused on jest@next. If you're still using jest 29.7.0, please use #15173 to discuss any additional workarounds needed for that version. 🙂