You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Populates your environment at **run-time** rather than **build-time**.
6
6
7
7
- Isomorphic - Server, browser and middleware compatible.
8
8
- Supports static site generation.
9
-
- Supports `.env`, just like [Next.js](https://nextjs.org/docs/basic-features/environment-variables).
9
+
- Supports `.env`, just like [Next.js][nextjs-env-vars].
10
10
11
-
Runtime environment variables are used in common best-practice patterns for building modern apps deployed via Docker. A big selling point of using Docker to begin with is to be able to build one image and have it work everywhere - dev, test, staging, production, etc - and having to "bake" in environment-specific configuration at build-time is antithetical to that goal. `next-runtime-env` aims to remove this hurdle by adding support for runtime environment variables to Next.js without sacrificing static site generation support.
11
+
Runtime environment variables are used in common best-practice patterns for
12
+
building modern apps deployed via Docker. A big selling point of using Docker to
13
+
begin with is to be able to build one image and have it work everywhere - dev,
14
+
test, staging, production, etc - and having to "bake" in environment-specific
15
+
configuration at build-time is antithetical to that goal. `next-runtime-env`
16
+
aims to remove this hurdle by adding support for runtime environment variables
17
+
to Next.js without sacrificing static site generation support.
12
18
13
19
### Getting started 🚀
14
20
15
21
1. Add the following lines to your `next.config.js`:
0 commit comments