From 612f06b7cf723a102cce7529aad13a0bae7abe8b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Dubois?= Date: Sat, 22 Apr 2017 15:57:09 +0300 Subject: [PATCH] Document skipping cache for babel-loader + setting env at runtime (#1747) --- examples/with-universal-configuration/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/examples/with-universal-configuration/README.md b/examples/with-universal-configuration/README.md index 78d7d2a3..66a6a313 100644 --- a/examples/with-universal-configuration/README.md +++ b/examples/with-universal-configuration/README.md @@ -30,4 +30,5 @@ This example show how to set custom environment variables for your application b ## 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. +- 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](https://github.com/zeit/next.js/issues/1103#issuecomment-279529809). +- 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](https://github.com/zeit/next.js/issues/1488#issuecomment-289108931).