Extraneous npm-check dependency in published package

[daltones]

I've just updated eslint-plugin-react from v7.8.2 to v7.9.0 and noticed a large change in my project's dependency tree.

That's because "npm-check": "5.7.1" appears as a dependency in the published package (although it isn't there in tag v7.9.0).

I certainly assume it shouldn't be there, right?

[ljharb]

https://unpkg.com/[email protected]/package.json indeed it does.

@yannickcr did you perhaps npm install npm-check without --no-save or --save-dev before publishing?

[ljharb]

I've published a v7.9.1, with updated deps, and the correct package.json.

[yannickcr]

Oh, my mistake. I should have better checked the package.json before publishing.

Thanks for the quick fix @ljharb.

[ljharb]

You may want to use npx npm-check rather than installing it in the future :-)