This project demonstrates using the setup generated by create-react-app alongside a Node Express API server.
We have a detailed blog post that explains this repository.
Check out the Node+Express if that's your preferred API server platform.
git clone [email protected]:fullstackreact/food-lookup-demo-rails.git
cd food-lookup-demo-rails
bundle
cd client
npm i
cd ..
rake start
create-react-app configures a Webpack development server to run on localhost:3000. This development server will bundle all static assets located under client/src/. All requests to localhost:3000 will serve client/index.html which will include Webpack's bundle.js.
To prevent any issues with CORS, the user and her browser will communicate exclusively with the Webpack development server.
Inside Client.js, we use Fetch to make a request to the API:
// Inside Client.js
return fetch(`/api/food?q=${query}`, {
// ...
})This request is made to localhost:3000, the Webpack dev server. Because the route has the special prefix /api/, the Webpack server knows that this request is actually intended for our API server. We specify in package.json that we would like Webpack to proxy API requests to localhost:3001:
// Inside client/package.json
"proxy": "http://localhost:3001/",This handy features is provided for us by create-react-app.
Therefore, the user's browser makes a request to Webpack at localhost:3000 which then proxies the request to our API server at localhost:3001:
This setup provides two advantages:
- If the user's browser tried to request
localhost:3001directly, we'd run into issues with CORS. - In many setups, this means that references to the API URL in development matches that in production. You don't have to do something like this:
// Example API base URL determination in Client.js
const apiBaseUrl = process.env.NODE_ENV === 'development' ? 'localhost:3001' : '/'This setup uses foreman for process management. Executing foreman start instructs Foreman to boot both the Webpack dev server and the API server.