-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Sibling packages in a repo conflict #134
Comments
Potentially related? #36 |
I find that I have similar issues - We store many front end widgets in a monorepo, and hooks being stored at a global level mean that a commit in a different subdirectory will trigger them. |
I think it's going to be tricky to handle such layout. What about adding a project/package.json with something like: {
"scripts": {
"precommit": "cd A && npm test && cd ../B && npm test"
},
"devDependencies": {
"husky": "^0.14.1"
}
} |
PR #13 is a bit old, but it might fix the issue. |
What's the status of this? |
@mcwebb |
Yes, containing only Husky and its dependencies. |
I kicked that root package idea around. Feel a little validated reading this. I really need to make the packages |
With a project repo structured like this:
If you
npm install
each of the packages, the last to be installed destructively takes over. Installing or uninstalling husky in one of the sibling projects overwrites the git hooks.Unless there is some clever config I am missing I won't be able to use husky :(
The text was updated successfully, but these errors were encountered: