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?
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?
I've published a v7.9.1, with updated deps, and the correct package.json.
Oh, my mistake. I should have better checked the package.json before publishing.
Thanks for the quick fix @ljharb.
You may want to use npx npm-check rather than installing it in the future :-)
Most helpful comment
You may want to use
npx npm-checkrather than installing it in the future :-)