From 9e6c9e36e3df87cad47efed8455c5a1bc9e9ad60 Mon Sep 17 00:00:00 2001 From: Robin Wieruch Date: Sat, 16 Dec 2017 14:15:05 +0800 Subject: [PATCH] Update README.md: When to use public folder --- packages/react-scripts/template/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/packages/react-scripts/template/README.md b/packages/react-scripts/template/README.md index c8bd3911fdc..3c20075bea8 100644 --- a/packages/react-scripts/template/README.md +++ b/packages/react-scripts/template/README.md @@ -723,6 +723,7 @@ The `public` folder is useful as a workaround for a number of less common cases: * You need a file with a specific name in the build output, such as [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest). * You have thousands of images and need to dynamically reference their paths. * You want to include a small script like [`pace.js`](http://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. +* You want to include (a) larger file(s) like `data.json` outside of the bundled code, because it shouldn't/[can't](https://github.com/facebookincubator/create-react-app/issues/2555) run through the build process. * Some library may be incompatible with Webpack and you have no other option but to include it as a `