- Displaying Lint Output in the Editor
- Getting Started with Storybook
- Analyzing the Bundle Size
- Using HTTPS in Development
- Adding a CSS Modules Stylesheet
- CSS Grid Layout prefixing is disabled by default, but it will not strip manual prefixing. If you’d like to opt-in to CSS Grid prefixing, first familiarize yourself about its limitations.
<link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">import('./moduleA') .then(({ moduleA }) => { // Use moduleA })- Adding Bootstrap
- Adding Relay
- Note: You must create custom environment variables beginning with REACT_APP
- Referencing Environment Variables in the HTML
- Adding Custom Environment Variables
- As the comment states, switching serviceWorker.unregister() to serviceWorker.register() will opt you in to using the service worker.
- We recommend to put the test files (or tests folders) next to the code they are testing so that relative imports appear shorter.
- If your app uses a browser API that you need to mock in your tests or if you just need a global setup before running your tests, add a src/setupTests.js to your project.
- Debugging Tests
- Proxying API Requests in Development
- Generating Dynamic Tags on the Server
- Injecting Data from the Server into the Page
- .env.staging, REACT_APP_API_URL, env-cmd
- Firebase, GitHub Pages, Heroku, Netlify, Now, S3, Surge
- If you’re ready to extract a component from your project so other people can use it, we recommend moving it to a separate directory outside of your project and then using a tool like nwb to prepare it for publishing.
- Pre-Rendering into Static HTML Files
- Advanced Configuration: BROWSER, HOST, PORT, HTTPS, PUBLIC_URL, CI, REACT_EDITOR, CHOKIDAR_USEPOLLING, GENERATE_SOURCEMAP, NODE_PATH, INLINE_RUNTIME_CHUNK
- instead of ejecting we recommend to fork react-scripts