d9060f5abd
### changes #### remove trailing spaces When I was using example I noticed trailing spaces. So, this PR removes the trailing spaces of json file, README, and others. `examples/with-jest-typescript/src/modules/cars/Overview.tsx` also has it, but this time it did not change as tslint error occurs at commit. |
||
|---|---|---|
| .. | ||
| pages | ||
| .env | ||
| next.config.js | ||
| package.json | ||
| README.md | ||
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
.envfile. - In this example, as soon as you reference an env var in your code it will be automatically be publicly available and exposed to the client.
- If you want to have more centralized control of what is exposed to the client check out the example with-universal-configuration-build-time.
- Env vars are set (inlined) at build time. If you need to configure your app on rutime check out examples/with-universal-configuration-runtime.