Skip to content

Commit

Permalink
Chore: Make warning about package-lock.json more clear
Browse files Browse the repository at this point in the history
  • Loading branch information
sapegin committed Apr 5, 2018
1 parent 7734ac4 commit 5190a0c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion dangerfile.js
Expand Up @@ -7,7 +7,7 @@ const lockfileChanged = danger.git.modified_files.includes('package-lock.json');
if (packageChanged && !lockfileChanged) {
warn(`Changes were made to \`package.json\`, but not to \`package-lock.json\`.
Perhaps you need to run \`npm install\` and commit changes in package-lock.json. Make sure you’re using npm 5+.`);
If you’ve changed any dependencies (added, removed or updated any packages), please run \`npm install\` and commit changes in package-lock.json file. Make sure you’re using npm 5+.`);
}

if (!packageChanged && lockfileChanged) {
Expand Down

0 comments on commit 5190a0c

Please sign in to comment.