Skip to content
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

03-pages > 01-building-your-application > 06-configuring > 12-error-h… #245

Merged
merged 2 commits into from
Jun 29, 2023

Conversation

ainochi-kor
Copy link
Contributor

@ainochi-kor ainochi-kor commented Jun 25, 2023

기여자용

문서 개선

Progress


Next.js provides a static 500 page by default to handle server-side errors that occur in your application. You can also [customize this page](/docs/pages/building-your-application/routing/custom-error#customizing-the-500-page) by creating a `pages/500.js` file.
Next.js는 기본적으로 애플리케이션에서 발생하는 서버 사이드 오류를 처리하기 위해 정적 500 페이지를 제공합니다. `pages/500.js` 파일을 생성함으로써 [사용자가 정의한 페이지](/docs/pages/building-your-application/routing/custom-error#customizing-the-500-page)를 사용할 수 있습니다.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

500 페이지라는 표현이 조금 어색한 것 같긴한데 더 나은 표현이 있을까요?


After creating an `ErrorBoundary` component, import it in the `pages/_app.js` file to wrap the `Component` prop in your Next.js application.
`ErrorBoundary` 컴포넌트를 생성한 후 `pages/_app.js` 파일에서 불러와서 Next.js 애플리케이션의 `Component` 프로퍼티를 감쌉니다.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wrap을 감싼다고 표현을 하는게 익숙해서 표현했는데 적절한 표현인지 궁금하네요.

@ChanghyeonYoon
Copy link
Contributor

ref #161

Copy link
Contributor

@ChanghyeonYoon ChanghyeonYoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

수고하셨습니다 리뷰 반영 부탁드립니다!


When there is a runtime error during the development phase of your Next.js application, you will encounter an **overlay**. It is a modal that covers the webpage. It is **only** visible when the development server runs using `next dev` via `pnpm dev`, `npm run dev`, or `yarn dev` and will not be shown in production. Fixing the error will automatically dismiss the overlay.
Next.js 애플리케이션의 개발 단계에서 런타임 오류가 발생하면, **오버레이**를 만나게 될 것입니다. 이는 웹페이지를 덮는 모달입니다. 오직 `next dev`를 통해 개발 서버가 실행될 때 (`pnpm dev`, `npm run dev` 또는 `yarn dev` 사용 시)에만 보이며, 프로덕션(실제 서비스)에서는 보이지 않습니다. 오류를 수정하면 오버레이는 자동으로 사라집니다.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only 가 원래 Bold 였으므로 스타일 유지해주세요!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

네! 알겠습니다!

@yoo-jimin127 yoo-jimin127 self-requested a review June 29, 2023 13:22
@yoo-jimin127
Copy link
Contributor

ref #161

Copy link
Contributor

@yoo-jimin127 yoo-jimin127 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !! 수고하셨습니다 :) 👍
추가로 번역 희망하시는 부분 신청해주셔도 됩니다!!

@yoo-jimin127 yoo-jimin127 merged commit d1a6e6e into Nextjs-kr:main Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants