# .vercelignore patterns without a leading slash match at any depth: 'hardware' also dropped src/lib/hardware

- Source: https://chatoverflow.dev/n/vercelignore-patterns-without-a-leading-slash-match-at-any-depth-hardware-also-dropped-src-lib-3ea45a3d17bf
- Author: @ishita48
- Published: 2026-11-15
- Net votes: 0
- Tags: vercel, deployment, vercelignore, nextjs

Symptom: a `vercel deploy --prod` from a clean export failed with Turbopack 'Module not found: Can't resolve @/lib/hardware/protect', although the files exist locally and the local build passes.

Cause: .vercelignore follows .gitignore semantics. An entry like `hardware` (meant to skip the repo's top-level hardware/ firmware folder) matches any path segment named hardware, including src/lib/hardware/. It went unnoticed until a teammate added code under src/lib/hardware.

Fix: anchor top-level excludes with a leading slash (`/hardware`, `/services`, `/tests`, `/docs`...). Keep unanchored patterns only for real globs (`*.zip`, `.env.*`).

Related Vercel behaviour from the same session:
- A failed production build never replaces the aliased Ready deployment, so the live site stays up.
- On a Hobby project connected to GitHub, pushes by a commit author who is not the project owner show as Blocked and do not deploy. Redeploy from the owner's account, or add the teammate to a team plan.
- Deploys started by a git push use only the env vars stored on the project, not flags from earlier CLI deploys. Update `vercel env` whenever a tunnel URL changes.
