Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Hook dispatcher breaks on Git for Windows when core.hooksPath is an absolute path

Open
  • Is something wrong?
#3,102 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
git, node.js, shell
Domain
cli, devtools

Research direction

Start by reading the generated .vite-hooks/_/h script described in the issue, then locate the code that generates it and any related hook tests. Reproduce on Windows with Git for Windows using an absolute core.hooksPath. Done means the generated dispatcher handles that path correctly and git commit runs the repository's hook without the reported module error or silently falling back to a global vp.

Written by the indexing model from the issue text.

Description

pending triage

Version: vite-plus 1.3.0 (global vp 1.2.0), Git for Windows 2.54.0, Node 22.23.1, Windows 11.

What happens

When core.hooksPath is an absolute Windows path such as C:\repo\.vite-hooks\_, every hook fails:

Error: Cannot find module 'C:\Program Files\Git\Users\me\repo\node_modules\vite-plus\bin\vp'
VITE+ - pre-commit script failed (code 1)

Some tools set an absolute path on purpose. For example, worktree managers point linked worktrees at the main checkout's dispatcher, because the generated .vite-hooks/_ is gitignored and missing in a new worktree.

Cause

The generated .vite-hooks/_/h derives the repo root from $0 and prepends it to PATH:

d="$(dirname "$(dirname "$(dirname "$0")")")"
export PATH="$d/node_modules/.bin:$PATH"

Git for Windows passes $0 as a drive-letter path, so d is C:\repo or C:/repo. sh splits the PATH entry at the drive colon into C and \repo\node_modules\.bin:

  • With backslashes, sh finds the pnpm shim through the drive-relative path. The shim then passes /repo/... to Node, which MSYS maps under the Git install root, giving the MODULE_NOT_FOUND above.
  • With forward slashes, the entry doesn't resolve, and vp silently falls back to whatever else is on PATH (here, the global ~/.vite-plus/bin/vp).

Repro

  1. On Windows with Git for Windows, run vp config --hooks in a repo whose pre-commit is vp staged.
  2. Run git config core.hooksPath "$(pwd -W)\.vite-hooks\_", or any C:\... absolute value.
  3. Run git commit.

Suggested fix

Normalise d (or $0) to a POSIX path before building PATH, for example:

case "$d" in [A-Za-z]:*) command -v cygpath >/dev/null 2>&1 && d=$(cygpath -u "$d") ;; esac

Alternatively, avoid putting a path derived from $0 into PATH. Husky uses the cwd-relative node_modules/.bin.

Workaround we use (documented init script ~/.config/vite-plus/hooks-init.sh):

case "$0" in
  [A-Za-z]:*)
    if [ -z "${VP_HOOKS_POSIX_REEXEC-}" ] && command -v cygpath >/dev/null 2>&1; then
      export VP_HOOKS_POSIX_REEXEC=1
      exec sh "$(cygpath -u "$0")" "$@"
    fi
    ;;
esac
Dominant language
Rust
Stars
6.3k
Forks
283
Avg merge
1d 14h
Merged PRs (30d)
208

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.