Inflight Deprecation Warning #12258
Comments
|
We should move this issue to https://github.com/sveltejs/svelte-preprocess as it comes from the ❯ npm why inflight
[email protected] dev
node_modules/inflight
inflight@"^1.0.4" from [email protected]
node_modules/glob
glob@"^7.1.3" from [email protected]
node_modules/rimraf
rimraf@"^2.5.2" from [email protected]
node_modules/sander
sander@"^0.5.0" from [email protected]
node_modules/sorcery
sorcery@"^0.11.0" from [email protected]
node_modules/svelte-preprocess
svelte-preprocess@"^5.1.3" from [email protected]
node_modules/svelte-check
dev svelte-check@"^3.6.0" from the root project |
|
Wouldn't the fix be to bump dependencies in https://github.com/Rich-Harris/sander, not svelte-preprocess? Or, perhaps, to just start using built-in filesystem APIs instead in https://github.com/Rich-Harris/sorcery? |
|
hello when i do the command to install nodered i have this error ,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. |
|
I'm getting this error while trying to install Appium, any idea how it can be resolved? 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. |
The author of inflight deprecated the package on Mar 22. isaacs/inflight-DEPRECATED-DO-NOT-USE#5 (comment) This is common with JavaScript since anyone can came up with a package and when it got deprecated we get a bunch of errors or warnings. |
|
@ananduremanan what should we do with the warnings that appear to us? |
If the package actually causes a memory leak, it would be a serious problem. The best we can do is find the package that uses inflight (as @eltigerchino mentioned in his comment), replace it with |
|
is this issue on windows devices only or with mac users too? |
I don't think so. When a package is deprecated it affects all users of that package, regardless of their operating system. |
|
I am also having this problem when upgrading Capacitor from v.5 to v.6. I am a mac user. |
|
You can run |
|
I have a problem when creating a project with Vite using the command |
|
I am also trying to install Appium and have gotten the same error message about inflight and a few other things. When I run I am a bit lost as to what to do next? Do we just wait for a fix? I am fairly new to this and totally new to automated testing |
I'm using a completely different project that depends on inflight as a sub-dependency, but I saw your post from a Google search and thought I'd pass along some information. I don't know anything about this project, but if it creates a package-lock.json after installation, you may be able to look in there to see what dependencies rely on it, and backtrack it to the parent one from there. That should give you your answer on which dependency is at fault. |
|
Hey guys! 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. I am a newbie in the coding space. Thank you! |
|
I think Updating glob and mocha in https://github.com/Rich-Harris/sander and https://github.com/Rich-Harris/sorcery may fix issues related to SvelteKit. Both of these packages use a lot of deprecated packages and haven't been updated for years. |
|
This is caused by |
just downgrade the node into 18 may things works because i did it in next js it works in 20 version but not in 22 or just remove eslint problem solve |
|
Temporary solution: add |
|
|
|
We should also probably remove |
with mac os too I got this error when installing whatsapp-wep.js package
|
|
All dependencies have now been removed from Now we'll need to either update |
|
Hello I have the same error I am new to this so I have no idea what should I do, do you guys have a solution or just wait for an update or something? |
Hi jexc. Yes, see #12258 (comment) . We’ll have to wait a bit before updating to get rid of this warning |
|
Hello, I am getting an npm deprecated warning in my NestJS project. Please help me get rid of this warning 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. |
|
Add this to package.json, remove node_modules and package-lock.json, then execute "overrides": {
"eslint": {
"@humanwhocodes/config-array": "npm:@eslint/config-array",
"file-entry-cache": "^8.0.0"
}
} |
|
Some warnings have gone, but some are still there. 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. |
|
You either did not do exactly what I suggested: |
|
@lorand-horvath |
|
You should not have to set overrides for eslint. Upgrade to eslint 9 instead. You can create a new SvelteKit project if you want to see an example of what it looks like to use eslint 9 |
|
@benmccann upgrading to eslint 9 causes npm error |
|
I wouldn't think you need |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
We have started working on a new major version of svelte-check to fix this issue. The new version will drop these dependencies and many others. It will be probably a few weeks until it's ready due to vacation schedules and other commitments, but I'm excited about the improvements. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
it looks like this issue comes up high when searching for the warning. Please refrain from posting help requests or adding "me too" comments |
|
fwiw i tried both 'override' workarounds (including removing node_modules, package-lock.json and re-running npm install each time) and neither affected the inflight memory leak error at all. i also find it strange that this has been happening FOR MONTHS in the default- "everybody should create a new project this way" method, and this is generating errors and memory leaks. isn't svelte more polished that it has something that can be expected to work out of the box? seems weird to be editing package.json for new project built from a template. i appreciate the hard work and svelte does seem pretty interesting, but it's frustrating when the most basic things w/a new project need immediate maintenance... esp for a framework that's supposed to be EASIER. |
|
https://github.com/sveltejs/language-tools/releases/tag/svelte-check-4.0.0 just released a few days ago and removes the dependency on the old version of EDIT: #12642 and #12638 solve this so we'll just need to cut a release after |
|
Yeah, I merged the fix on Monday, but hadn't cut a release yet. I just did that now, so new projects should no longer generate these warnings. If you encounter this, please upgrade your project to This was difficult to fix because we had to fix so many different dependencies and cut major releases of multiple packages. We've really reduced the number of dependencies by a lot during this process so that we're much less likely to hit these types of issues in the future. Compare https://npmgraph.js.org/?q=svelte-check@4 vs https://npmgraph.js.org/?q=svelte-check@3. There are plans to remove a majority of the remaining dependencies by upgrading to the upcoming chokidar v4 when it is released. |
This comment was marked as off-topic.
This comment was marked as off-topic.
If you’re experiencing this issue and you’re not using SvelteKit or svelte check, we cannot help you. |
and others
Describe the bug
On Installing dependencies after
npm create svelte@latestI gotnpm 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. Not sure if it is serious or not, sawleaks memoryin it thus opened this issue.Reproduction
By Installing dependencies after
npm create svelte@latest.Logs
No response
System Info
System: OS: Windows 11 10.0.22631 CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U Memory: 4.47 GB / 15.73 GB Binaries: Node: 18.18.0 - C:\Program Files\nodejs\node.EXE npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD Browsers: {} npmPackages: @sveltejs/adapter-auto: latest => 3.2.1 @sveltejs/kit: latest => 2.5.10 @sveltejs/vite-plugin-svelte: latest => 3.1.0 svelte: latest => 4.2.17 vite: latest => 5.2.11Severity
annoyance
Additional Information
No response
The text was updated successfully, but these errors were encountered: