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
Everytime you try to commit/push code, husky complains about where scripts are located.
When does this occur?
git commit & git push
Where on the platform does it happen?
<root>
How do we replicate the issue?
Clone the repo
npm i
echo 'whatever' >> README.md
git add README.md
git commit -m "Trying to commit"
The latest command passes if you're using node > 8, but shows these notes:
Warning: Setting pre-commit script in package.json > scripts will be deprecated
Please move it to husky.hooks in package.json, a .huskyrc file, or a husky.config.js file
Or run ./node_modules/.bin/husky-upgrade for automatic update
Expected behavior (i.e. solution)
Moving hasky-specific scripts to a hasky key inside package.json should fix the issues.
Note that, as said, commits cannot pass if you're using node < 8.
What version of OC, Node.js and OS are you using?
OC: From git, at HEAD
Node.js: Version 6, as specified in .nvmrc. As said, using version > 8 allows the commit to pass.
OS: Ubuntu 18.04
The text was updated successfully, but these errors were encountered:
Who is the bug affecting?
Everyone who tries to change OC code.
What is affected by this bug?
Everytime you try to commit/push code, husky complains about where scripts are located.
When does this occur?
git commit & git push
Where on the platform does it happen?
<root>
How do we replicate the issue?
The latest command passes if you're using node > 8, but shows these notes:
Expected behavior (i.e. solution)
Moving hasky-specific scripts to a
hasky
key insidepackage.json
should fix the issues.Note that, as said, commits cannot pass if you're using node < 8.
What version of OC, Node.js and OS are you using?
.nvmrc
. As said, using version > 8 allows the commit to pass.The text was updated successfully, but these errors were encountered: