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
next.js/examples/with-universal-configuration
History
Tim Neutkens cf130c70f0 Prefix process.env to avoid inconsistency (#2647)
2017-07-26 20:39:21 +02:00
..
pages Prefix process.env to avoid inconsistency (#2647) 2017-07-26 20:39:21 +02:00
.babelrc Added universal configuration example (#991) 2017-02-05 04:43:23 +05:30
env-config.js Prefix process.env to avoid inconsistency (#2647) 2017-07-26 20:39:21 +02:00
package.json Normalize example package.json files (#2350) 2017-06-23 10:46:44 +02:00
README.md Document skipping cache for babel-loader + setting env at runtime (#1747) 2017-04-22 14:57:09 +02:00

README.md

Deploy to now

With universal configuration

How to use

Download the example or clone the repo:

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

Install it and run:

npm install
npm run dev

Deploy it to the cloud with now (download)

now

The idea behind the example

This example show how to set custom environment variables for your application based on NODE_ENV using transform-define.

Caveats

  • Because a babel plugin is used the output is cached in node_modules/.cache by babel-loader. When modifying the configuration you will have to manually clear this cache to make changes visible. Alternately, you may skip caching for babel-loader as shown here.
  • This example sets the environment configuration at build time, meaning the same build might not be used in e.g. both staging and production. For a solution which sets the environment at runtime, see here.