Created by: rwieruch
I ran into this issue as well where I had to use a public folder to make larger (2mb) files (.json) available to my application via the public folder and a symlink to the files in the node_modules folder (how to, issues). Just added this use case to the list of "When to use a public folder" for others in case they run into it as well.
Closed by
(Jul 25, 2025 4:36am UTC)
Activity
Created by: facebook-github-bot
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.
If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!
added CLA Signed label
Created by: rwieruch
Never mind. It's not working this way (as shown in "how to") for .json files as well. They are still used by the build step and leads to
JavaScript heap out of memory. Now I started to include the .json files in the index.html, but this isn't an elegant solution either, because I would have to load the json asynchronously in my JavaScript file afterward.<script id="data" type="application/json" src="%PUBLIC_URL%/someData.json"></script>Maybe there is anyway to get it into the script tags body, then it could be loaded synchronously in JavaScript?
