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

02-app > 02-api-reference > 05-next-config.js > env.mdx 번역 초안 #312

Merged
merged 5 commits into from
Jul 5, 2023

Conversation

lydiacho
Copy link
Contributor

@lydiacho lydiacho commented Jun 27, 2023

기여자용

문서 개선

Progress

@haileyport
Copy link
Member

ref #110

Copy link
Member

@YuriKwon YuriKwon left a comment

Choose a reason for hiding this comment

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

수고하셨습니다! 👍🏻
리뷰 확인 부탁드려요:)

@@ -1,20 +1,20 @@
---
title: env
description: Learn to add and access environment variables in your Next.js application at build time.
description: 빌드 시 Next.js 애플리케이션에서 환경 변수를 추가하고 액세스하는 방법을 알아보세요.
Copy link
Member

Choose a reason for hiding this comment

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

영어를 최소화하기 위해 액세스 -> 접근으로 변경하면 더 좋을 것 같습니다.


- [With env](https://github.com/vercel/next.js/tree/canary/examples/with-env-from-next-config-js)

</details>

> **Good to know**: environment variables specified in this way will **always** be included in the JavaScript bundle, prefixing the environment variable name with `NEXT_PUBLIC_` only has an effect when specifying them [through the environment or .env files](/docs/pages/building-your-application/configuring/environment-variables).
> **참고**: 이러한 방식으로 지정된 환경 변수는 **항상** 자바스크립트 번들에 포함되며, 환경 변수 이름 앞에 `NEXT_PUBLIC_`를 붙이면 [환경 또는 .env 파일을 통해 지정된 경우](/docs/pages/building-your-application/configuring/environment-variables)에만 영향을 미칩니다.
Copy link
Member

Choose a reason for hiding this comment

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

  1. 발음을 고려하여 NEXT_PUBLIC_를 -> NEXT_PUBLIC_
    로 수정 부탁드려요!

  2. [through the environment or .env files]와 일치하도록
    [환경 또는 .env 파일을 통해 지정된 경우] -> [환경 또는 .env 파일을 통해]
    로 괄호의 범위를 변경하면 좋을 것 같습니다.

@@ -24,7 +24,7 @@ module.exports = {
}
```

Now you can access `process.env.customKey` in your code. For example:
이제 아래와 같이 코드에서 `process.env.customKey` 에 액세스할 수 있습니다.
Copy link
Member

Choose a reason for hiding this comment

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

위와 동일하게 액세스 -> 접근으로 수정 부탁드립니다!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@YuriKwon 말씀하신 부분 모두 수정 완료하였습니다!

Copy link
Member

@YuriKwon YuriKwon left a comment

Choose a reason for hiding this comment

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

LGTM! 고생하셨습니다!
추가로 번역 희망하시면 이슈에 댓글로 남겨주세요!:)

@YuriKwon YuriKwon merged commit bd2a4e4 into Nextjs-kr:main Jul 5, 2023
@YuriKwon YuriKwon mentioned this pull request Jul 5, 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.

None yet

4 participants