From ef94b0561d5afb9b50b905fa5cd3f94e965c69c0 Mon Sep 17 00:00:00 2001 From: Dan Abramov <dan.abramov@gmail.com> Date: Thu, 25 Aug 2016 14:40:49 +0100 Subject: [PATCH] Prepare for 0.2.3 release --- template/README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/template/README.md b/template/README.md index ed745e73c..4dd68fcd6 100644 --- a/template/README.md +++ b/template/README.md @@ -392,8 +392,7 @@ We will consider integrating more tightly with Flow in the future so that you do ## Adding Custom Environment Variables -**Note: this feature will be available with `react-scripts@0.3.0` and higher.** -**It is not released yet, but it will be a part of a future release.** +>Note: this feature is available with `react-scripts@0.2.3` and higher. Your project can consume variables declared in your environment as if they were declared locally in your JS files. By default you will have `NODE_ENV` defined for you, and any other environment variables starting with @@ -467,8 +466,7 @@ Check out [this tutorial](https://www.fullstackreact.com/articles/using-create-r ## Proxying API Requests in Development -**Note: this feature will be available with `react-scripts@0.3.0` and higher.** -**It is not released yet, but it will be a part of a future release.** +>Note: this feature is available with `react-scripts@0.2.3` and higher. People often serve the front-end React app from the same host and port as their backend implementation. For example, a production setup might look like this after the app is deployed: -- GitLab