The hooks configuration example used a format that was valid when
originally written but broke across two Claude Code releases:
- v1.0.41: Added `hook_event_name` to hook input, replacing the
previous field name. The hook script was still reading `.event`,
causing the case statement to always fall through to unknown.
- v2.1.63: Added HTTP hooks with `{ "type": "command", "command": "..." }`
object format. Bare string paths in the hooks array are no longer
valid now that hook type disambiguation is required.
Changes:
- Stop hooks now use the full matcher/hooks object structure
- PostToolUse inner hooks use typed command objects
- Hook script reads `hook_event_name` instead of `event`
Ref: https://docs.anthropic.com/en/docs/claude-code/hooks
|
||
|---|---|---|
| .. | ||
| app | ||
| i18n | ||
| messages | ||
| public | ||
| .env.example | ||
| .gitignore | ||
| bun.lock | ||
| eslint.config.mjs | ||
| middleware.ts | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.mjs | ||
| README.md | ||
| tsconfig.json | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.