如何部署带有Node.js后端的React.js应用？是否需要在后端运行build命令？

Hey there! Let's walk through deploying your React.js frontend + Node.js backend app, and answer that build command question clearly.

First: Handle the React Frontend #

Before deploying, you must run the build command in your React project—this is non-negotiable. Here's why:

• In your React project root, run npm run build. This compiles all your React code, components, and assets into a static build folder full of plain HTML, CSS, and JS files. These static files are what get served to users' browsers.

You have two main options for hosting these static files:

• Option 1: Host separately
  Deploy the build folder to a static hosting service (like Nginx, Vercel, or Netlify). Then configure your React app to send API requests to your deployed Node backend.
• Option 2: Host with your Node backend
  Have your Node server serve the React static files directly. This keeps everything on one deployment. Use Express's static middleware to do this—here's a quick example:

  const express = require('express');
  const path = require('path');
  const app = express();
  
  // Serve React's static files
  app.use(express.static(path.join(__dirname, '../client/build')));
  
  // Your API routes go here
  app.get('/api/data', (req, res) => {
    res.json({ message: 'Hello from the backend!' });
  });
  
  // Catch all other routes and return React's index.html (for SPA routing)
  app.get('*', (req, res) => {
    res.sendFile(path.join(__dirname, '../client/build/index.html'));
  });
  
  app.listen(process.env.PORT || 3000);
  

Next: Deploy the Node.js Backend #

Now, to your big question: Do you need to run a build command in the backend environment?
The short answer: Only if your Node code requires compilation.

• If your backend is written in plain JavaScript (no TypeScript, no untranspiled ES6+ features that older Node versions don't support), you don't need a build command. Just deploy your source files (skip node_modules—install dependencies on the server with npm install --production for a leaner setup).
• If you're using TypeScript, or tools like Babel to transpile modern JS, then yes—you'll need to run your build command (like tsc or a custom npm run build script) to convert your code into plain JS that Node can execute. Then deploy the compiled output (usually a dist or build folder) instead of the source files.

When deploying the backend:

• Use a process manager like PM2 to keep your server running continuously (instead of just node server.js, which will stop if the connection drops). Install PM2 globally with npm install -g pm2, then start your server with pm2 start server.js.
• Make sure to set up environment variables (like database credentials, API keys) on your deployment server—don't hardcode them!

Final Tips for Smooth Deployment #

• CORS Handling: If your frontend and backend are on different domains, add the cors middleware to your Node server to allow cross-origin requests:

  const cors = require('cors');
  app.use(cors());
  

• API URL Configuration: In your React app, use environment variables (like REACT_APP_API_URL in .env.production) to point to your production backend, not localhost. This way you don't have to hardcode the URL.

内容的提问来源于stack exchange，提问作者test app