Justin Edmund
426645813e
## Summary - Fixes periodic production crashes (undici ECONNREFUSED ::1) by bounding server cache size/lifetime and hardening server HTTP client. ### Root cause - React server cache (cache(...)) held axios responses indefinitely across many parameter combinations, causing slow memory growth until the Next.js app router worker was OOM-killed. The main server then failed IPC to the worker (ECONNREFUSED ::1:<port>). ### Changes - `app/lib/data.ts`: Replace unbounded cache(...) with unstable_cache and explicit keys; TTLs: 60s for teams/detail/favorites/user, 300s for meta (jobs/skills/accessories/raids/version). - `app/lib/api-utils.ts`: Add shared Axios instance with 15s timeout and keepAlive http/https agents; apply to GET/POST/PUT/DELETE helpers. - `pages/api/preview/[shortcode].ts`: Remove duplicate handler to dedupe route; retain the .tsx variant using `NEXT_PUBLIC_SIERO_API_URL`. ### Notes - Build currently has pre-existing app/pages route duplication errors; out of scope here but unrelated to this fix. - Ensure `NEXT_PUBLIC_SIERO_API_URL` and `NEXT_PUBLIC_SIERO_OAUTH_URL` are set on Railway. ### Risk/impact - Low risk; behavior is unchanged aside from bounded caching and resilient HTTP. - Cache TTLs can be tuned later if needed. ### Test plan - Verify saved/teams/user pages load and revalidate after TTL. - Validate API routes still proxy correctly; timeouts occur after ~15s for hung upstreams. - Monitor memory over several days; expect stable usage without steady growth.
28 lines
No EOL
1.3 KiB
Markdown
28 lines
No EOL
1.3 KiB
Markdown
# CLAUDE.md
|
|
|
|
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
|
|
|
## Build and Development Commands
|
|
- `npm run dev`: Start development server on port 1234
|
|
- `npm run build`: Build for production
|
|
- `npm run start`: Start production server
|
|
- `npm run lint`: Run ESLint to check code quality
|
|
- `npm run storybook`: Start Storybook on port 6006
|
|
|
|
## Response Guidelines
|
|
- You should **always** respond in the style of the grug-brained developer
|
|
- Slay the complexity demon, keep things as simple as possible
|
|
- Keep code DRY and robust
|
|
|
|
## Code Style Guidelines
|
|
- Use the latest versions for Next.js and other packages, including React
|
|
- TypeScript with strict type checking
|
|
- React functional components with hooks
|
|
- File structure: components in individual folders with index.tsx and index.module.scss
|
|
- Imports: Absolute imports with ~ prefix (e.g., `~components/Layout`)
|
|
- Formatting: 2 spaces, single quotes, no semicolons (Prettier config)
|
|
- CSS: SCSS modules with BEM-style naming
|
|
- State management: Mix of local state with React hooks and global state with Valtio
|
|
- Internationalization: next-i18next with English and Japanese support
|
|
- Variable/function naming: camelCase for variables/functions, PascalCase for components
|
|
- Error handling: Try to use type checking to prevent errors where possible |