NPM Warnings for Meteor 3.1?

help
1

I’m updating from M3.0.1 to M3.1. I ran Meteor reset and I deleted the old node_modules folder and package-lock.json file.

I ran meteor npm install. It worked but there are a few warnings I’d like to understand more about. Here are the first two warnings:

meteor npm install
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 @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead

I ran meteor npm ls inflight to find out what was loading it and got this:

meteor npm ls inflight
myFolder /path/to/my/project
└─┬ @meteorjs/eslint-config-meteor@1.0.5
  └─┬ eslint@8.57.1
    └─┬ file-entry-cache@6.0.1
      └─┬ flat-cache@3.2.0
        └─┬ rimraf@3.0.2
          └─┬ glob@7.2.3
            └── inflight@1.0.6

Is there a more recent version of @meteorjs/eslint-config-meteor?

Then I ran this:

meteor npm ls humanwhocodes
myFolder /path/to/my/project
└── (empty)

There’s no entry for humanwhocodes in my package.json file. That’s odd-- why am I getting a warning on it if it isn’t even in my project? :thinking:

2

meteor npm ls @humanwhocodes/config-array

1 Like
3

Inflight should be completely harmless in this context, since it is used by eslint, we will be removing it from there too in the future, I believe we already removed completely from the core.

4

Thanks! It’s in eslint:

└─┬ eslint@8.57.1
└── @humanwhocodes/config-array@0.13.0