[Bug]: inflight deprecated, glob deprecated

[ChronoBoot]

Version

29.7.0

Steps to reproduce

npm i jest --save

Expected behavior

No warning

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
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

Additional context

The inflight archive has not been updated since 8 years and has an alternative which is up to date https://www.npmjs.com/package/lru-cache
The used glob version is deprecated and 2 years old

Is there specific reasons why these have not been replaced/updated ?

Environment

System:
    OS: macOS 14.5
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Binaries:
    Node: 22.3.0 - ~/.nvm/versions/node/v22.3.0/bin/node
    Yarn: 1.22.22 - ~/.yarn/bin/yarn
    npm: 10.8.1 - ~/.nvm/versions/node/v22.3.0/bin/npm
    pnpm: 6.11.0 - ~/.nvm/versions/node/v14.19.0/bin/pnpm
  npmPackages:
    jest: ^29.7.0 => 29.7.0

[qbantek]

#14509 should remove this warning.

[Jme797]

There is also a memory leak issue in inflight that is not patched

[belinde]

Seeing the distributed package jest-config 29.7.0, it seems that jest-config is still dependent on glob ^7.1.3

This is the package.json taken from an installation in a project of mine:
package.json

[wingedthing]

jest/reporters v29.7.0 is still depending on glob ^7.1.3 and is causing the dependency along with inflight to be pulled into projects requiring jest v29.7.0:

jest/packages/jest-reporters/package.json

Line 25 in 4e56991

"glob": "^7.1.3",

[ankitbavne]

I am getting the following warning in my NestJS backend project. Even after updating all the packages, I am still encountering this warning. Is there anyone who can help me get rid of it?

PS F:\Test_project\rescueworld-microservice-retteracademy> npm i
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
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

[wingedthing]

I am getting the following warning in my NestJS backend project. Even after updating all the packages, I am still encountering this warning. Is there anyone who can help me get rid of it?

@ankitbavne If you're on npm version 8 or higher, you can use overrides in your package.json:

  "overrides": {
    "glob": "10.4.2" 
  }

This will force jest to use that version in your build.

[ankitbavne]

@wingedthing
Is it safe to use overrides ?

[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.

[msaeedsaeedi]

Waiting for the fix

[LvckyAPI]

waiting for the fix

[maka-io]

Waiting for fix

[crisu]

Waiting for fix. thank you

[danilobraga-loft]

Waiting for fix. thank you

[ahakkar]

Bumping to keep this unfixed issue alive.

[mtycholaz]

Waiting on a fix

[vpzomtrrfrt]

Looks like jest-reporters has updated to glob 10 in the 30.0.0 alpha, but the old version is still pulled in by babel-plugin-istanbul: istanbuljs/babel-plugin-istanbul#294

[ThePlenkov]

Here is my dependency:

@nx/[email protected]
  └─┬ @jest/[email protected]
    └─┬ [email protected]
      └── [email protected]

[lsaudon]

Waiting on a fix

[odbalogun]

Waiting on a fix

[vpzomtrrfrt]

what is going on with these comments?

[ThePlenkov]

i honestly don't know from where it comes - but I noticed that in yarn.lock there was still a reference to inflight packages used by outdated glob versions. So I created MR to override the version to 10.3.10 which is used currently in the project, but not sure if it will actually impact published packages because I don't know how jest is publishing them. I see that build folder gets created right in packages - and it shares original package.json of the subpackage with a built code. Therefore to resolve glob properly i guess we also need to do something with that package.json too ( or with yarn.lock of that published package probably ).