docs: update guide for schema validation on build for Next.js 15 #282
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@chungweileong94 is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
juliusmarminge
requested changes
Jan 25, 2025
Comment on lines
+110
to
+125
| We recommend you importing your newly created file in your `next.config.ts`. This will make sure your environment variables are validated at build time which will save you a lot of time and headaches down the road. | ||
|
|
||
| ```ts title="next.config.ts" | ||
| import type { NextConfig } from "next"; | ||
|
|
||
| // Import env here to validate during build. | ||
| import "./app/env"; | ||
|
|
||
| const nextConfig: NextConfig = { | ||
| /** ... */ | ||
| }; | ||
| ``` | ||
|
|
||
| <Callout type="info"> | ||
|
|
||
| If you’re using Next.js version 14 or below, you can use [unjs/jiti](https://github.com/unjs/jiti) to import TypeScript files in your `next.config.js`: |
There was a problem hiding this comment.
if we should have this it should alos come with a warning about the shortcomings of using esm in next.config.ts. for example import.meta.dirname etc is undefined. i recommend sticking to js config until they fix this
There was a problem hiding this comment.
@juliusmarminge is this also the case when using "type": "module" in the package.json file?
There was a problem hiding this comment.
yes - it's how they transpile the next.config.ts that's the problem, they call it out in their docs
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.
Since now that Next.js 15 supports TypeScript for
next.config.ts, we no longer needjitifor importing schema TS file. We will update the guide for Next.js 15, while still keeping the old guide for Next.js 14 or below.fix #281