Problem Statement:
The repository root contains a .vite/deps_temp_8e5c994c/ directory, a scratch/ directory, and an output/pdf/ directory tracked in git. .vite/deps_temp_* is Vite's auto-generated dependency pre-bundling cache — it is regenerated on every dev-server start and should never be committed. scratch/ reads as a leftover local development workspace, and output/pdf/ appears to be generated scan-report output.
Why this matters:
Committing build caches means every fresh clone starts with a stale, potentially inconsistent Vite cache that doesn't match the contributor's actual dependency tree — this can cause "works on my machine" bugs that are hard to diagnose. It also bloats repo size unnecessarily and clutters the root directory for new contributors trying to understand the actual project layout (the README's own "Repository Map" doesn't mention scratch/ or output/ as meaningful directories).
Proposed Solution:
Add .vite/, scratch/, and output/ (or scope more precisely if output/ is meant to be a real feature, e.g. output/* with a .gitkeep) to .gitignore.
Run git rm -r --cached .vite scratch output/pdf to untrack them without deleting local copies.
If scratch/ was serving a real documented purpose (e.g., a contributor scratchpad convention), document that explicitly in CONTRIBUTING.md instead of committing its contents.
Impact: Clean, reproducible fresh-clone experience — important for a project explicitly positioning itself (per the README) as "Contributor-friendly... for students and GSSoC contributors."
Problem Statement:
The repository root contains a .vite/deps_temp_8e5c994c/ directory, a scratch/ directory, and an output/pdf/ directory tracked in git. .vite/deps_temp_* is Vite's auto-generated dependency pre-bundling cache — it is regenerated on every dev-server start and should never be committed. scratch/ reads as a leftover local development workspace, and output/pdf/ appears to be generated scan-report output.
Why this matters:
Committing build caches means every fresh clone starts with a stale, potentially inconsistent Vite cache that doesn't match the contributor's actual dependency tree — this can cause "works on my machine" bugs that are hard to diagnose. It also bloats repo size unnecessarily and clutters the root directory for new contributors trying to understand the actual project layout (the README's own "Repository Map" doesn't mention scratch/ or output/ as meaningful directories).
Proposed Solution:
Add .vite/, scratch/, and output/ (or scope more precisely if output/ is meant to be a real feature, e.g. output/* with a .gitkeep) to .gitignore.
Run git rm -r --cached .vite scratch output/pdf to untrack them without deleting local copies.
If scratch/ was serving a real documented purpose (e.g., a contributor scratchpad convention), document that explicitly in CONTRIBUTING.md instead of committing its contents.
Impact: Clean, reproducible fresh-clone experience — important for a project explicitly positioning itself (per the README) as "Contributor-friendly... for students and GSSoC contributors."