feat: verify environment variables #4115
Open
+2,695
−2,622
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.
Description
Use @t3-oss/env-core zod to verify environment variables. When the environment variables fail to be read, an error will be reported when starting the project, ensuring the integrity of the necessary parameters required when the project is started.
At the same time, the environment variables exposed on the body have been removed and exposed through the recommended method of nextjs.
dify/web/app/layout.tsx
Lines 39 to 44 in 13cd409
dify/web/app/layout.tsx
Lines 43 to 44 in 13cd409
Type of Change
Please delete options that are not relevant.
@t3-oss/env-core
andzod
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
There are no destructive updates. Although environment variables need to be checked, a default .env file is generated during installation. This modification can be said to only add a type hint to the environment variable.
Suggested Checklist:
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint gods