-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. #15087
Comments
Looks like the warning originates from Jest's dependencies. These are updated with each version. I just checked, installing |
Is there any appropriate workaround for people who don't use alpha/beta/gamma/non-stable versions? |
I think Yarn's |
It seems that the issue needs someone more competent. The mentioned package is out of date. The last update was 8 years ago and all versions contain memory leaks. |
It's from |
This is true. But all packages that depend on 29.7.0 (almost all packages) are currently unsafe. And jest@next is still a alpha version at the moment. |
It's a breaking change to update to newer versions of |
I keep receiving the same warning! They should release a secure version of Jest until they complete their v30. |
I don't agree that fix security issue cannot be done. It must be done. contains glob v10.3.10 while the glob v10.3.10 does not use inflight library So there are literally 0 reasons to close the issue |
Where do you see security issue? The warning mentioned in the OP says: "This module is not supported, and leaks memory." If there are any security issues, better open another issue. |
I tried
While Unfortunately there's not an updated version of |
|
That one was already fixed in #14509. Which I think you know already. |
@anomiex it is not fixed in the stable version(https://github.com/jestjs/jest/blob/v29.7.0/packages/jest-reporters/package.json#L25). I think you know that people do not use alpha version in production. |
And I think you know that continuing to complain about that isn't going to accomplish anything with the Jest maintainers. They won't make the change in the v29 branch because it would require dropping support for old nodejs versions, as they already told you, so it has to wait for v30. OTOH, my comment, if they don't ignore it because it was buried by your complaining, points out something that still isn't fixed in |
let's check jest v29 node versions
what about glob v10?
As far as I understand, both support nodejs v14 and there is no need to drop support for old nodejs versions. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version
29.7.0
Steps to reproduce
I was installing jest and NPM hit me with this message:
I have not tested for validity of any memory leaks, but I think it's worth looking into for the devs. Sorry I can't give any more information.
Expected behavior
NPM Shouldn't warn me about a package that has memory leaks that Jest depends on.
Actual behavior
NPM Does give me a warning about memory leaks.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: