Allow vp config to install hooks without forcing vp staged #2252

Activity

1. Perdolique

   added

   pending triage

   on Jul 25, 2026
2. Perdolique

   added the

   Bug

   issue type on Jul 25, 2026
3. liangmiQwQ commented on Jul 27, 2026

   

   liangmiQwQ

   on Jul 27, 2026

   Collaborator

   More actions

   Hello!

   At the present, vp config forces the hooks must include vp staged. That said, you can still modify your <project-root>/.vite-hooks/pre-commit to add other commands.

   Like

   vp staged
   vp run lint
   vp exec tsc --noEmit

   It is just a small .includes('vp staged') string match, so there is a small workaround if you don't really want to use vp staged

   # vp staged
   vp run lint
   vp exec tsc --noEmit

   Considering the current vp config's behavior is documented and expected. I will treat it as a feature request :), and I think it is worth supporting!
4. liangmiQwQ

   changed the issue type from

   Bug

   to

   Feature

   on Jul 27, 2026
5. Perdolique commented on Jul 27, 2026

   

   Perdolique

   on Jul 27, 2026

   Last edited by Perdolique

   Author

   More actions

   @liangmiQwQ, I still consider it a bug. I don't want to use "staged" at all, only commands in the hooks, similar to husky, but vp config is forcing it:

   The config (or lacking of a config file at all)

   export default defineConfig({});
   

   becomes

   export default defineConfig({
     staged: {
       "*": "vp check --fix"
     }
   });
   

   every time a new user clones the repo. This section should be optional. At the moment, it's a blocker for migration from husky.

   ---

   As a workaround, I did:

   export default defineConfig({
     staged: {
       '*': (): string[] => []
     }
   })
   

   But it looks like an unnecessary crutch, to be honest 🤔.
6. liangmiQwQ commented on Jul 27, 2026

   

   liangmiQwQ

   on Jul 27, 2026

   Collaborator

   More actions

   cc @TheAlexLichter
7. liangmiQwQ commented on Jul 27, 2026

   

   liangmiQwQ

   on Jul 27, 2026

   Collaborator

   More actions

   every time a new user clones the repo.

   Cloning repo itself shouldn't trigger git hooks. Maybe you mean vp install?

   ---

   As a workaround, I did:

   export default defineConfig({
     staged: {
       '*': (): string[] => []
     }
   })
   

   @Perdolique Maybe you can try leave an empty object for staged, like staged: {}.
8. Perdolique commented on Jul 27, 2026

   

   Perdolique

   on Jul 27, 2026

   Last edited by Perdolique

   Author

   More actions

   Yes, vp install, which one is triggering prepare. It looks like the empty staged also works. For some reason, the absence of this option generates a new rule on vp install right after a fresh clone, even if the config file exists.
9. TheAlexLichter commented on Jul 27, 2026

   

   TheAlexLichter

   on Jul 27, 2026

   Last edited by TheAlexLichter

   Member

   More actions

   How about this:

   • vp config should only install and refresh the generated hook dispatcher under .vite-hooks/_. It should not modify hooks such as .vite-hooks/pre-commit and does not write to vite.config.ts.
   • Top-level .vite-hooks/* scripts are project-owned and live in the repo (committed), while .vite-hooks/_/* stays ignored and is recreated after installation
   • vp create can continue scaffolding a default vp staged pre-commit hook and staged configuration when the user opts into that workflow
   • vp migrate should preserve or translate existing behavior (e.g. from husky) and only introduce defaults when there is no existing hook policy

   That would allow custom hooks without requiring an empty staged configuration or a new opt-out flag.

   👍React with 👍1Reacted by Liang
10. Perdolique commented on Jul 27, 2026

    

    Perdolique

    on Jul 27, 2026

    Last edited by Perdolique

    Author

    More actions

    @TheAlexLichter, yes. It sounds exactly like how husky works right now. Currently, I have a config just for an empty staged: {} as a workaround for hooks.

    👍React with 👍1Reacted by Alexander Lichter
11. liangmiQwQ

    added

    enhancementNew feature or requestNew feature or request

    and removed

    pending triage

    on Jul 27, 2026
12. TheAlexLichter

    self-assigned this

    on Jul 28, 2026
13. fengmk2

    added this to the RC milestone on Aug 4, 2026
14. fengmk2

    added a commit that references this issue on Aug 4, 2026

    fix(cli): preserve project-owned git hooks (#2280)

    ...

    This issue will close once commit cfb59b2 is merged into the 'main' branch.

    cfb59b2
15. fengmk2

    closed this as completedin #2280on Aug 4, 2026