Repository navigation
fix: 배포 직후 홈 배너·에디터 추천이 비어 보이는 문제 수정 - #910
Merged
Merged
Conversation
…e not empty after deploy The home route was prerendered at build time. The CI build cannot reach the internal product API (ENOTFOUND product-api), so banners and editor's picks were baked in empty and served until the 5-minute revalidation regenerated the page. Render on request instead; the API responses keep their fetch revalidate cache. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bottle-note/workspace#547
관련 이슈 (Related Issue)
PR 타입 (Type of Change)
증상
개발 서버에 #906을 배포한 직후 홈에서 서버에서 불러오는 배너와 에디터 추천만 비어 보임. 몇 분 뒤 다시 들어가면 정상.
원인
/)은 빌드 때 미리 만드는 정적 페이지였음 (빌드 결과○ /, 5분 revalidate)[internalApi] 공개 데이터 조회 실패 /v2/curations/feed?... getaddrinfo ENOTFOUND product-api변경 사항 (Changes)
src/app/(primary)/page.tsx:export const dynamic = 'force-dynamic'— 요청 시 렌더링 (app/sitemap.ts와 같은 방식)next.revalidate를 각 fetch에 명시해 force-dynamic에서도 데이터 캐시 사용)src/app/(primary)/page.vitest.test.ts: 홈이 요청 시 렌더링으로 설정돼 있는지 확인 (되돌리면 실패하는 것 확인)테스트 방법 (Test Procedure)
pnpm next build→ 결과표에서/가ƒ (Dynamic)인지 확인pnpm next start후 홈 요청 3회 → 매번 HTML에 배너·에디터 추천 데이터 포함.next/cache/fetch-cache파일이 다시 쓰이지 않음 → API 응답 캐시 재사용 확인셀프 체크리스트 (Self Checklist)
pnpm lint통과참고 사항 (Additional Information)
<html id="__next_error__">로 내려옴 — 서버 렌더링 중 오류로 클라이언트에서 다시 그리는 상태. 이번 변경과 무관한 기존 문제라 별도로 조사 필요🤖 Generated with Claude Code