Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/expatfile/next-runtime-env
Next.js Runtime Environment Configuration - Populates your environment at runtime rather than build time.
https://github.com/expatfile/next-runtime-env
Last synced: 3 months ago
JSON representation
Next.js Runtime Environment Configuration - Populates your environment at runtime rather than build time.
- Host: GitHub
- URL: https://github.com/expatfile/next-runtime-env
- Owner: expatfile
- License: mit
- Created: 2023-04-30T14:15:20.000Z (over 1 year ago)
- Default Branch: development
- Last Pushed: 2024-04-12T17:57:46.000Z (8 months ago)
- Last Synced: 2024-04-13T00:50:52.821Z (8 months ago)
- Language: TypeScript
- Homepage: https://www.npmjs.com/package/next-runtime-env
- Size: 36.1 MB
- Stars: 257
- Watchers: 2
- Forks: 6
- Open Issues: 18
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
![GitHub branch checks state][build-url] [![codecov][cov-img]][cov-url] [![Known Vulnerabilities][snyk-img]][snyk-url]
# 🌐 Next.js Runtime Environment Configuration
**Effortlessly populate your environment at runtime, not just at build time, with `next-runtime-env`.**
🌟 **Highlights:**
- **Isomorphic Design:** Works seamlessly on both server and browser, and even in middleware.
- **Next.js 13 & 14 Ready:** Fully compatible with the latest Next.js features.
- **`.env` Friendly:** Use `.env` files during development, just like standard Next.js.
### 🤔 Why `next-runtime-env`?
In the modern software development landscape, the "[Build once, deploy many][build-once-deploy-many-link]" philosophy is key. This principle, essential for easy deployment and testability, is a [cornerstone of continuous delivery][fundamental-principle-link] and is embraced by the [twelve-factor methodology][twelve-factor-link]. However, front-end development, particularly with Next.js, often lacks support for this - requiring separate builds for different environments. `next-runtime-env` is our solution to bridge this gap in Next.js.
### 📦 Introducing `next-runtime-env`
`next-runtime-env` dynamically injects environment variables into your Next.js application at runtime. This approach adheres to the "build once, deploy many" principle, allowing the same build to be used across various environments without rebuilds.
### 🤝 Compatibility Notes
- **Next.js 14:** Use `[email protected]` for optimal caching support.
- **Next.js 13:** Opt for [`[email protected]`][app-router-branch-link], tailored for the App Router.
- **Next.js 12/13 Page Router:** Stick with [`[email protected]`][pages-router-branch-link].
### 🔖 Version Guide
- **1.x:** Next.js 12/13 Page Router
- **2.x:** Next.js 13 App Router
- **3.x:** Next.js 14 with advanced caching
### 🚀 Getting Started
In your `app/layout.tsx`, add:
```js
// app/layout.tsx
import { PublicEnvScript } from 'next-runtime-env';
export default function RootLayout({ children }) {
return (
{children}
);
}
```
The `PublicEnvScript` component automatically exposes all environment variables prefixed with `NEXT_PUBLIC_` to the browser. For custom variable exposure, refer to [EXPOSING_CUSTOM_ENV.md](docs/EXPOSING_CUSTOM_ENV.md).
### 🧑💻 Usage
Access your environment variables easily:
```tsx
// app/client-page.tsx
'use client';
import { env } from 'next-runtime-env';
export default function SomePage() {
const NEXT_PUBLIC_FOO = env('NEXT_PUBLIC_FOO');
return NEXT_PUBLIC_FOO: {NEXT_PUBLIC_FOO};
}
```
### 🛠 Utilities
Need to expose non-prefixed environment variables to the browser? Check out [MAKING_ENV_PUBLIC.md](docs/MAKING_ENV_PUBLIC.md).
### 👷 Maintenance
`next-runtime-env` is proudly maintained by [Expatfile.tax](expatfile-site), the leading US expat tax e-filing software.
### 📚 Acknowledgments
Kudos to the [react-env](react-env-repo) project for the inspiration, and a shoutout to @andonirdgz for the innovative context provider idea!
---
[build-url]: https://img.shields.io/github/checks-status/expatfile/next-runtime-env/main
[cov-img]: https://codecov.io/gh/expatfile/next-runtime-env/branch/main/graph/badge.svg?token=mbGgsweFuP
[cov-url]: https://codecov.io/gh/expatfile/next-runtime-env
[snyk-img]: https://snyk.io/test/github/expatfile/next-runtime-env/badge.svg
[snyk-url]: https://snyk.io/test/github/expatfile/next-runtime-env
[nextjs-env-vars-order]: https://nextjs.org/docs/basic-features/environment-variables#environment-variable-load-order
[build-once-deploy-many-link]: https://www.mikemcgarr.com/blog/build-once-deploy-many.html
[fundamental-principle-link]: https://cloud.redhat.com/blog/build-once-deploy-anywhere
[twelve-factor-link]: https://12factor.net
[pages-router-branch-link]: https://github.com/expatfile/next-runtime-env/tree/1.x
[app-router-branch-link]: https://github.com/expatfile/next-runtime-env/tree/2.x
[nextjs-env-vars]: https://nextjs.org/docs/basic-features/environment-variables
[react-env-repo]: https://github.com/andrewmclagan/react-env
[expatfile-site]: https://expatfile.tax