New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Strict mode doesn't check for mismatching #23

Closed

glukki opened this issue May 29, 2019 · 0 comments · Fixed by #33

glukki commented May 29, 2019 •

edited

If package is locked, but mismatch, the npmvet -s -r ci exit without error.

This may happen in development, when you update your branch with the latest master, that brings new packages, and forget to run npm ci.

I made a PR with the fix.

The text was updated successfully, but these errors were encountered:

glukki mentioned this issue

Fix strict mode not failing on mismatch #24

Closed

andrewhathaway mentioned this issue

Merged

andrewhathaway closed this as completed in #33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment