feat: add /dist/ to .gitignore during vinext init

[vikas5914]

Summary

• vinext init now adds /dist/ to .gitignore (Step 6 in the init flow)
• Creates .gitignore if it doesn't exist, appends the entry if missing, skips if already present
• Preserves all existing .gitignore entries

Changes

• packages/vinext/src/init.ts: Added updateGitignore() function, wired into init() as Step 6, added updatedGitignore to InitResult, added summary log line
• tests/init.test.ts: Added 8 new tests — 5 unit tests for updateGitignore() and 3 integration tests for the full init flow

Why

vite build outputs to /dist/ by default. Without this entry in .gitignore, users who run vinext init and then build will end up with build artifacts tracked in git.

[southpolesteve]

/bigbonk review this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vinext@220

commit: ac85ea2

[ask-bonk]

Clean implementation — the function is well-structured, tests are thorough, and it integrates naturally into the init flow. One edge case worth considering and a couple minor notes below.

[ask-bonk]

Review posted. Here's a summary of my feedback:

Main concern: The duplicate detection only checks for the exact string /dist/ (with leading slash). Many projects — including this repo's own .gitignore — use dist/ (without the leading slash), which is actually a broader pattern. If a user already has dist/ in their .gitignore, updateGitignore would add a redundant /dist/ entry. I suggested broadening the check to also recognize dist/ and dist as already covering the dist directory.

Minor notes:

• Suggested adding a test case for the dist/ (no leading slash) variant
• Small naming nit on the entry variable if the broader matching is adopted

Otherwise the PR is clean: the function handles file creation, appending, no-trailing-newline, and idempotency correctly. Tests are comprehensive with both unit and integration coverage, and all 54 tests pass.

github run

[vikas5914]

@southpolesteve updated RR with changes from bigbonk.