-
Notifications
You must be signed in to change notification settings - Fork 1
Refactor(client): 이미지 최적화 및 코드 스플리팅 #205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
코드 스플리팅 구현 완료, 에러 처리 확인 필요
단계별 컴포넌트에 대한 lazy loading 구현이 올바르게 되어 있습니다. 이를 통해 초기 번들 크기가 감소하고 각 단계가 필요할 때만 로드됩니다.
다만, lazy-loaded 컴포넌트의 로드 실패(네트워크 오류, 빌드 문제 등)를 처리하기 위한 Error Boundary가 현재 파일에 보이지 않습니다. 상위 컴포넌트에 Error Boundary가 구현되어 있는지 확인해 주세요.
다음 스크립트를 실행하여 상위 컴포넌트에서 Error Boundary 구현 여부를 확인하세요:
🏁 Script executed:
Length of output: 114
🏁 Script executed:
Length of output: 3413
🏁 Script executed:
Length of output: 1154
Lazy-loaded 컴포넌트에 Error Boundary 추가 필요
코드 스플리팅 구현은 올바르게 되어 있으나, 검증 결과 lazy-loaded 컴포넌트의 로드 실패를 처리하기 위한 Error Boundary가 없습니다.
현재 구조:
OnBoarding.tsx에서 Error Boundary 없이<MainCard />를 직접 사용MainCard.tsx에서 네 개의 step 컴포넌트를 lazy() 및 Suspense로 감싸고 있음OnBoarding.tsx또는MainCard.tsx에 Error Boundary를 추가하여 lazy component 로드 실패에 대한 안정성을 확보하세요.