Files
copilotkit__copilotkit/.gitignore
Tyler Slaton 04c6383990 fix(shell-docs): resolve launch.json port collision + harden preview script + untrack next-env.d.ts
`.claude/launch.json` declared port 3000 for both \`docs\` (Next.js at
docs/) and \`shell\` (Next.js at showcase/shell/) — only one could
actually start at a time, and Next's auto-port-fallback would land
\`shell\` on whatever was free without the launch config knowing.
Reassign \`shell\` to port 3004 (next free slot after the existing
3001/2/3 cluster) and pass \`-- --port 3004\` through \`npm run dev\`
so the runtime port matches the declared port.

\`.claude/preview/shell-docs.sh\` had a blanket
\`|| { echo "(may have failed — expected)" }\` after \`pnpm install\` that
swallowed every install failure, not just the documented \`lefthook\`
prepare-hook one. A real failure (network down, lockfile drift) would
get silently absorbed and then explode much later at the \`npx tsx\`
generator step with a confusing \`Cannot find module\` error. Verify
\`$SCRIPTS_DIR/node_modules\` exists after the install attempt; bail
with a clear instruction if it doesn't.

\`showcase/shell-docs/next-env.d.ts\` is a Next.js-auto-generated file
whose contents differ between \`next dev\` (\`./.next/dev/types/...\`)
and \`next build\` (\`./.next/types/...\`). Per Next.js's own
recommendation it should never be checked in — the v16 path change
would otherwise produce dirty trees on every build/dev switch, and a
clean checkout's typecheck would fail because the imported
\`.next/dev/types/routes.d.ts\` is itself gitignored. Add the file to
\`.gitignore\` (matching the existing \`docs/next-env.d.ts\` entry) and
\`git rm --cached\` to untrack the committed copy. Next regenerates it
on first \`next dev\`/\`next build\`.

Call-site enumeration:
- \`.claude/launch.json\` — no callers within the repo; the
  \`/run\` slash command reads it as data. Port change is non-breaking
  for any other tooling that doesn't bind to 3000 for \`shell\`.
- \`.claude/preview/shell-docs.sh\` — the lefthook installer is the
  only thing that runs it (besides interactive users); both flows
  benefit from the loud failure.
- \`next-env.d.ts\` — no source file imports from it; the file is a
  TypeScript \`/// <reference\` declaration consumed by tsc only,
  regenerated on each build/dev.
2026-05-20 20:01:16 -07:00

77 lines
1.0 KiB
Plaintext

# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
.vscode
.chalk
.claude/*.local.json
.claude/worktrees
# misc
.DS_Store
*.pem
__snapshots__
@generated
node_modules
.pnpm-store
.idea/
cdk_outputs.json
.nx
test-run-comment.md
superpowers/
*.egg-info/
.installed.cfg
*.egg
**/.langgraph_api
*.sqlite
*.sqlite-shm
*.sqlite-wal
__pycache__/
*.env
.doctest-output/
*.next
.venv
.vercel
docs/next-env.d.ts
showcase/shell-docs/next-env.d.ts
# Showcase: staged shared contexts for Docker builds (see showcase/scripts/dev-local.sh)
showcase/integrations/*/shared_python/
showcase/integrations/*/shared_typescript/
# External repos (cloned for development)
ext-apps/
dist
.nx
.angular
build
debug-storybook.log
storybook-static
coverage
.turbo
.langgraph_api
lefthook-local.yml
.husky/
.langgraph_api
# Private agent instructions (not shared with the team)
private-agents.md
# Release artifacts
release-notes.md
release-notes-notion.json
# Binary artifacts
*.dSYM/
*.exe
*.dll
*.so
*.dylib
*.o
*.obj
*.a
*.lib
*.wasm
tasks/