How does husky manage shared folder configuration

[laterdayi]

Currently husky is one in each project.husky directory,

With more and more projects, copying directories can cause a lot of trouble. Is there a way to share.husky directories

[laterdayi]

@typicode Looking forward to your help

[typicode]

Git only has one hooks directory so you can't have natively multiple places where hooks are stored. The recommended approach is to have husky in root and let monorepo tools run scripts.

So for example, in A/package.json, B/package.json you would have a pre-commit script that would be run with your monorepo tool.

https://typicode.github.io/husky/#/?id=monorepo

[laterdayi]

@typicode 但是在package.json中无法直接使用 pre-commit，好像还是需要在.husky中创建对应的hooks文件

[laterdayi]

Is there a way to put the SH file on NPM and use it in the project, can you give a DEMO?

[typicode]

Sorry I probably won't have time right now to go into details, but I hope to be able to make a blog post or add docs at some points.
Meanwhile, you can script husky and do something like that:

// my-script.js
const yourHooks = require('your-hooks') // your hooks is a published package on npm
const husky = require('husky')

husky.install()
// loop through your hooks and do something like run husky.set('.husky/pre-commit', yourHooks.preCommit)

In your package.json

"scripts": {
  "prepare": "node my-script"
}

[laterdayi]

@typicode
in npm scripts prepare, is ok
However, post-merge requires creating a post-merge file in the.husky of the local project to implement the post-merge directive