Inflight Deprecation Warning

[anandhuremanan]

Describe the bug

On Installing dependencies after npm create svelte@latest I got npm warn deprecated inflight@1.0.6: 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, saw leaks memory in 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.11

Severity

annoyance

Additional Information

No response

[eltigerchino]

We should move this issue to https://github.com/sveltejs/svelte-preprocess as it comes from the sorcery dependency svelte-preprocess relies on.

❯ npm why inflight
inflight@1.0.6 dev
node_modules/inflight
  inflight@"^1.0.4" from glob@7.2.3
  node_modules/glob
    glob@"^7.1.3" from rimraf@2.7.1
    node_modules/rimraf
      rimraf@"^2.5.2" from sander@0.5.1
      node_modules/sander
        sander@"^0.5.0" from sorcery@0.11.0
        node_modules/sorcery
          sorcery@"^0.11.0" from svelte-preprocess@5.1.4
          node_modules/svelte-preprocess
            svelte-preprocess@"^5.1.3" from svelte-check@3.7.1
            node_modules/svelte-check
              dev svelte-check@"^3.6.0" from the root project

[Conduitry]

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?

[aymanin]

hello when i do the command to install nodered i have this error ,npm warn deprecated inflight@1.0.6: 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 npmlog@5.0.1: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated gauge@3.0.2: This package is no longer supported.
what i can do?thank you

[ranaaboubakr]

I'm getting this error while trying to install Appium, any idea how it can be resolved?

npm warn deprecated inflight@1.0.6: 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 npmlog@7.0.1: This package is no longer supported.
npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported
npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported.
npm warn deprecated gauge@5.0.2: This package is no longer supported.

[anandhuremanan]

I'm getting this error while trying to install Appium, any idea how it can be resolved?

npm warn deprecated inflight@1.0.6: 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 npmlog@7.0.1: This package is no longer supported. npm warn deprecated rimraf@2.4.5: Rimraf versions prior to v4 are no longer supported npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported. npm warn deprecated gauge@5.0.2: This package is no longer supported.

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.

[Srossiprieto]

@ananduremanan what should we do with the warnings that appear to us?

[anandhuremanan]

@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 lru-cache as the author of inflight suggests, and open a pull request. Alternatively, we could wait for some cool guy from the open-source community(like @Conduitry above) to fix it.

[ranaaboubakr]

is this issue on windows devices only or with mac users too?

[anandhuremanan]

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.

[BrunaMarjorie]

I am also having this problem when upgrading Capacitor from v.5 to v.6. I am a mac user.

[eltigerchino]

You can run npm why inflight or pnpm why inflight to figure out which packages are depending on the deprecated package. In svelte-check’s case we will probably fix it by removing the dependency on inflight; replacing it with native APIs or a different package.

[Srossiprieto]

I have a problem when creating a project with Vite using the command npm create vite@latest. I go through all the configuration steps, but when I run the command npm install, I get warnings. This started happening after I followed a tutorial that used ESLint with the command npx eslint --init. Since then, these warnings have appeared in each of my projects. Would you like me to run any command so you can see what might be going wrong?

[KikoB10]

I am also trying to install Appium and have gotten the same error message about inflight and a few other things. When I run npm why inflight terminal says ' no dependencies found matching inflight'

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

[SugarD-x]

I am also trying to install Appium and have gotten the same error message about inflight and a few other things. When I run npm why inflight terminal says ' no dependencies found matching inflight'

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.

[Chefkochcooking]

Hey guys!
I'm working on an web app rn and thus installed bun in VSCode.
The installation was successfully but I am still concerned about those lines...

npm warn deprecated inflight@1.0.6: 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 rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

I am a newbie in the coding space.
Any steps to solve this problem?

Thank you!
ChiefCook