Great question! Breaking up your monolithic server.js into separate route files is a key step toward a maintainable, scalable API. Let’s walk through the process with a user routes example, then cover how to extend this to other resource collections.

Step 1: Create a Dedicated Route File (e.g., user-routes.js) #

First, I recommend organizing all routes in a dedicated routes/ folder for clarity—create routes/user-routes.js and use Express’s Router to define all user-related endpoints:

// routes/user-routes.js
const express = require('express');
const router = express.Router();

// Example user routes
router.get('/', (req, res) => {
  res.json({ message: 'Fetch all users' });
});

router.get('/:userId', (req, res) => {
  res.json({ message: `Fetch user with ID: ${req.params.userId}` });
});

router.post('/', (req, res) => {
  res.json({ message: 'Create new user', userData: req.body });
});

router.put('/:userId', (req, res) => {
  res.json({ message: `Update user ${req.params.userId}`, updatedData: req.body });
});

router.delete('/:userId', (req, res) => {
  res.json({ message: `Delete user ${req.params.userId}` });
});

module.exports = router;

Step 2: Mount the Route File in server.js #

Now head back to your main server.js file, import the user routes, and mount them to a base URL using app.use():

// server.js
const express = require('express');
const app = express();

// Import your route files
const userRoutes = require('./routes/user-routes');

// Required middleware (e.g., parse JSON bodies)
app.use(express.json());

// Mount user routes to a dedicated path
app.use('/api/users', userRoutes);

// Server setup
const PORT = process.env.PORT || 3000;
app.listen(PORT, () => {
  console.log(`Server running on port ${PORT}`);
});

Now all user routes will live under http://localhost:3000/api/users, http://localhost:3000/api/users/123, etc.—cleanly separated from your core server setup!

Step 3: Extend to Other Route Collections #

The exact same pattern works for any other resource in your API (posts, products, orders, etc.). For example, create routes/post-routes.js:

// routes/post-routes.js
const express = require('express');
const router = express.Router();

router.get('/', (req, res) => {
  res.json({ message: 'Fetch all posts' });
});

router.post('/', (req, res) => {
  res.json({ message: 'Create new post', postData: req.body });
});

// Add more post-specific routes here

module.exports = router;

Then mount it in server.js:

const postRoutes = require('./routes/post-routes');
app.use('/api/posts', postRoutes);

Bonus: Separate Route Logic from Controller Logic (Even Better!) #

For maximum modularity, split your route handler functions into dedicated controller files. This keeps route files focused on endpoint definitions, while controllers handle the actual business logic.

1. Create controllers/userController.js:

// controllers/userController.js
exports.getAllUsers = (req, res) => {
  // Add database queries or business logic here
  res.json({ message: 'Fetch all users' });
};

exports.getUserById = (req, res) => {
  const userId = req.params.userId;
  // Add user fetch logic here
  res.json({ message: `Fetch user with ID: ${userId}` });
};

// Add create, update, delete functions here...

2. Update user-routes.js to use the controller:

// routes/user-routes.js
const express = require('express');
const router = express.Router();
const userController = require('../controllers/userController');

router.get('/', userController.getAllUsers);
router.get('/:userId', userController.getUserById);
router.post('/', userController.createUser);
// ... and so on

module.exports = router;

This setup makes your code easier to debug, test, and scale as your API grows.

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