Next.js integration

[yamcodes]

This issue tracks a potential Next.js integration for ArkEnv, following a similar philosophy to the Vite and Bun plugins.

Related discussion: #611 (contains useful insights by @shadyar-bakr)

Goals

• Provide first-class Next.js integration without coupling ArkEnv core to Next.js
• Prevent server-only env access from client components
• Maintain typesafety and validation guarantees

Non-goals

• Adding client/server separation logic to the core library
• Replacing Next.js error handling or env conventions

Open questions

• withArkEnv(nextConfig) vs standalone helper
• How to handle app router vs pages router
• Build-time vs runtime enforcement boundaries
• Is it considered a "plugin"? (Not sure Next.js even has a plugin system)
• What should we call it? @arkenv/nextjs?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Request: Framework integration #611

Related Issues

• ArkEnv in vite.config.ts #365
• .env linter #481

🔗 Related PRs

#155 - Docs improvements [merged]
#382 - Support type definitions created with type() in createEnv [merged]
#459 - Update Bun example for plugin and add Bun+React example [merged]

👤 Suggested Assignees

• yamcodes
• shadyar-bakr

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!