Skip to content

Conversation

@kamdubiel
Copy link
Contributor

@kamdubiel kamdubiel commented Nov 6, 2025

Description

  • Deleted next-runtime-env and replaced it with super simple next-public-env
  • Updated the Environment Variables.md docs
  • Splt the env validation to separate server (secret) and client (public) validators
  • Changed the way .env* files are picked up by the frontend apps, it's now following Next.js docs order
  • Added nonce and CSP rules
  • Fixed some minor warnings / errors that I missed during last Next.js update, and once that were required after adding nonces

Screenshots/Videos

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@kamdubiel kamdubiel self-assigned this Nov 6, 2025
@kamdubiel kamdubiel changed the title feat: Remove environment variables handling feat: Improve environment variables handling Nov 6, 2025
Copy link
Member

@DarkoKukovec DarkoKukovec left a comment

Choose a reason for hiding this comment

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

Nice!

@kamdubiel kamdubiel merged commit 64ad399 into main Nov 7, 2025
1 check passed
@kamdubiel kamdubiel deleted the feat/remove-next-runtime-env branch November 7, 2025 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants