NodeJS createServer如何识别Express应用对象中设置的自定义端口？为何需在Express中配置port参数？

Great question! Let's unpack this clearly, since it's a common point of confusion with the Express generator's default code.

1. It's a convention, not an Express core requirement #

Express 4.x's official settings table doesn't list port as a built-in setting—and that's totally fine. This line comes from the Express generator's opinionated setup, not something the Express framework itself enforces.

2. The actual purpose of app.set('port', port) #

The main goal here is centralizing your port configuration:

• Instead of repeating the process.env.PORT || '3000' logic everywhere you need the port number, you store it once in the app's settings.
• Anywhere else in your code (like logging middleware, custom error handlers, or routes that need to reference the app's port), you can fetch it with app.get('port') instead of redefining the variable.

3. Does the Node.js server object use this setting? Short answer: No #

Look back at your code:

var server = http.createServer(app);
server.listen(port);

The server.listen() call uses the port variable you defined earlier, not the value stored in app.set('port'). The Node.js HTTP server has no idea about Express's app settings—it only cares about the argument you pass to listen().

So why does the generator include app.set('port', port) then? Because the generator's default error-handling code relies on it. For example, the auto-generated onError function might use app.get('port') to format error messages consistently:

function onError(error) {
  if (error.syscall !== 'listen') throw error;
  
  // Use the stored port value to create a user-friendly error message
  var bind = typeof app.get('port') === 'string'
    ? `Pipe ${app.get('port')}`
    : `Port ${app.get('port')}`;

  switch (error.code) {
    case 'EACCES':
      console.error(`${bind} requires elevated privileges`);
      process.exit(1);
    case 'EADDRINUSE':
      console.error(`${bind} is already in use`);
      process.exit(1);
    default:
      throw error;
  }
}

To sum up #

app.set('port', port) is a convenience convention from the Express generator. It's not required to run your server, but it makes your code cleaner by centralizing the port value for use in other parts of your application (like logging or error handling). The Node.js HTTP server itself doesn't use this setting directly—it just uses the port variable you pass to server.listen().

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