You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/npm/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ You can run an audit on your node project by simply running `npm audit`. This wi
55
55
56
56
Note that commonly the issues are found in *development* dependencies (e.g. jest in this case). Since these aren't are a part of your production deployments, most likely your production application is not vulnerable. But still good practice to keep vulnerabilities to `0`.
57
57
58
-
Simply add `npm audit` as a part of your deployment to ensure the projects stay up to date.
58
+
Simply add `npm audit`(the command exist with error code `1` in case of error) as a part of your deployment to ensure the projects stay up to date.
59
59
60
60
## Public vs. Private packages
61
61
You don't need this when *using* any of the common public npm packages. Just know its there for enterprise / commercial customers.
0 commit comments