rsnext/examples/with-dotenv
Juan Olvera 7e12997af6 Test updater script on examples folder (#5993)
I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.:

```
$ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0"
```

This PR contains the result against the examples folder.
2019-01-05 12:19:27 +01:00
..
pages Add prettier for examples directory (#5909) 2018-12-17 17:34:32 +01:00
.env with-dotenv example (#2399) 2017-06-29 08:32:45 +02:00
next.config.js Add prettier for examples directory (#5909) 2018-12-17 17:34:32 +01:00
package.json Test updater script on examples folder (#5993) 2019-01-05 12:19:27 +01:00
README.md Rewrite with-dotenv example (#4924) 2018-08-08 09:01:00 -07:00

Deploy to now

With Dotenv example

How to use

Using create-next-app

Execute create-next-app with Yarn or npx to bootstrap the example:

npx create-next-app --example with-dotenv with-dotenv-app
# or
yarn create next-app --example with-dotenv with-dotenv-app

Download manually

Download the example:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-dotenv
cd with-dotenv

Install it and run:

npm install
npm run dev
# or
yarn
yarn dev

Deploy it to the cloud with now (download)

now

The idea behind the example

This example shows how to inline env vars.

Please note:

  • It is a bad practice to commit env vars to a repository. Thats why you should normally gitignore your .env file.
  • As soon as you are using an env var in your code it will be publicly available and exposed to the client.
  • If you want to have more control of what is exposed to the client check out tusbar/next-runtime-dotenv.
  • Env vars are set (inlined) at build time. If you need to configure your app on rutime check out examples/with-universal-configuration-runtime