-
Notifications
You must be signed in to change notification settings - Fork 388
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
npm WARN deprecated [email protected] #2609
Comments
same on Node.js version 22.2.0 |
that is a transitive dependency it's used by As long as you don't use the asset feature, you don't need to worry about it. nest-cli/lib/compiler/assets-manager.ts Lines 139 to 140 in 77c3e45
I guess we can't do much on our side |
I had the same issue when installing nest cli on mac os m3:
|
|
|
Same error Macbook Air M2, any ideas why is this happening?
|
btw this is being tracked here: shelljs/shelljs#1149 |
I cant use vite, react or Next.js right now do i need to update something ?> '_Wisdom\my-app\node_modules.bin' is not recognized as an internal or external command, Error: Cannot find module 'C:\Users\USER\Desktop\Webprojects\next\dist\bin\next' Node.js v20.11.0 |
i also currently facing this error .How to resolve it ? |
"Deprecated" does not mean "wrong" or "bad"; it simply means that you
should use something that is maintained because it will no longer be
maintained.
…On Tue, Jun 25, 2024 at 5:03 PM MalahimHaseeb ***@***.***> wrote:
i also currently facing this error .How to resolve it ?
npm warn deprecated ***@***.***: 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 @***@***.***: Use
@eslint/config-array instead
npm warn deprecated ***@***.***: Rimraf versions prior to v4 are no
longer supported
npm warn deprecated ***@***.***: Glob versions prior to v9 are no longer
supported
npm warn deprecated @***@***.***: Use
@eslint/object-schema instead
—
Reply to this email directly, view it on GitHub
<#2609 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKCF4ZT6OZBA25RGQBH4S3ZJIAL5AVCNFSM6AAAAABIFJLKCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQGIZTAOBQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@adeboyega, " 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." |
Is there an existing issue for this?
Current 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.
Minimum reproduction code
Since this happens with CLI usage, I don't see how I can provide meaningful reproduction code.
Steps to reproduce
Expected behavior
wihtout warning
Package version
10.3.2
NestJS version
No response
Node.js version
20.13.1
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: