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.

Sign up for GitHub

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

docs(nextjs): add config for standalone output #292

Merged
merged 2 commits into from
Jan 25, 2025
Merged

docs(nextjs): add config for standalone output #292

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8edc143
docs(nextjs): add config for standalone output
ezeparziale Dec 14, 2024
903f338
Merge branch 'main' into main
juliusmarminge Jan 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/src/app/docs/nextjs/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,24 @@ export const env = createEnv({

</Callout>

<Callout type="info">

If you're using the `standalone` output in your `next.config.ts`, make sure to include the following:

```ts title="next.config.ts"
import type { NextConfig } from "next"

const nextConfig: NextConfig = {
output: "standalone",
// Add the packages in transpilePackages
transpilePackages: ["@t3-oss/env-nextjs", "@t3-oss/env-core"],
}

export default nextConfig
```

</Callout>

### Validate schema on build (recommended)

We recommend you importing your newly created file in your `next.config.js`. 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. You can use [unjs/jiti](https://github.com/unjs/jiti) to import TypeScript files in your `next.config.js`:
Expand Down
Loading