terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity

Update with-dotenv example README.md to add troubleshooting information (#2995)

Browse source
This commit is contained in:
José Netto 2017-09-26 18:06:29 -03:00 committed by Tim Neutkens
parent 094bb1f7b9
commit 362fcf917a
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
examples/with-dotenv/README.md
View file

@ -29,3 +29,13 @@ now
This example shows the most basic idea of babel replacement from multiple environment. We have 1 env variable: `TEST` which will be replaced in development env and in production env with different babel plugin. In local development, babel reads .env file and replace process.env.* in your nextjs files. In production env (such as heroku), babel reads the ENV and replace process.env.* in your nextjs files. Thus no more needed to commit your secrets anymore.
Of course, please put .env* in your .gitignore when using this example locally.
## Troubleshooting
### Environment variables not showing on the page
If for some reason the variable is not displayed on the page, try clearing the `babel-loader` cache:
```
rm -rf ./node_modules/.cache/babel-loader
```