NodeJS后端Web应用数据库连接异步导出未定义问题求助

Ah, I see exactly what's going on here—you're hitting a classic asynchronous timing issue in Node.js! The MongoClient.connect method runs asynchronously, so its callback won't execute until the database connection is (successfully or unsuccessfully) established. But Node.js processes module exports synchronously, which means when module.exports = db runs, the db variable hasn't been assigned yet—it's still undefined.

Let's walk through a few solid solutions to fix this, depending on your preference and MongoDB driver version:

Solution 1: Export a Promise for the Connection #

Wrap your connection logic in a Promise, so any module that needs the database instance can wait for the connection to complete using await or .then().

const MongoClient = require('mongodb').MongoClient;

// Create a promise that resolves to the database connection
const dbPromise = new Promise((resolve, reject) => {
  MongoClient.connect('mongodb://localhost:27017/WIGAMEX', { poolSize: 50 }, (err, database) => {
    if (err) {
      console.log('Error opening global mongo connection');
      reject(err); // Pass the error to callers
    } else {
      console.log('MongoDB connection established');
      resolve(database); // Resolve with the connected db instance
    }
  });
});

module.exports = dbPromise;

How to use this: #

In modules that need the database:

// Inside an async function
const db = await require('./your-db-file');

// Or using .then() if you can't use async/await
require('./your-db-file')
  .then(db => {
    // Perform database operations here
  })
  .catch(err => {
    // Handle connection errors
  });

Solution 2: Export a Reusable Connection Getter Function #

This approach caches the connection once it's established, so you don't re-create connections every time you need the database.

const MongoClient = require('mongodb').MongoClient;

let db; // Cached connection instance

function getDb() {
  // If we already have a connection, return it immediately
  if (db) {
    return Promise.resolve(db);
  }

  // Otherwise, create a new connection
  return new Promise((resolve, reject) => {
    MongoClient.connect('mongodb://localhost:27017/WIGAMEX', { poolSize: 50 }, (err, database) => {
      if (err) {
        console.log('Error opening global mongo connection');
        reject(err);
      } else {
        db = database; // Cache the connection
        resolve(db);
      }
    });
  });
}

module.exports = getDb;

How to use this: #

const getDb = require('./your-db-file');

// In an async function
const db = await getDb();

// Or with .then()
getDb().then(db => {
  // Use the database
}).catch(err => {
  // Handle errors
});

Solution 3: Use Modern Async/Await with MongoDB 4.x+ #

If you're using MongoDB driver version 4.x or higher, MongoClient.connect returns a Promise directly, so you can clean up the code with async/await:

const MongoClient = require('mongodb').MongoClient;

let db;

async function connectDb() {
  if (!db) {
    try {
      // Connect to the client (driver 4.x+ returns a client instance)
      const client = await MongoClient.connect('mongodb://localhost:27017/WIGAMEX', { poolSize: 50 });
      // Get the database instance from the client
      db = client.db('WIGAMEX');
      console.log('MongoDB connected successfully');
    } catch (err) {
      console.log('Error opening global mongo connection:', err);
      throw err; // Let callers handle the error
    }
  }
  return db;
}

module.exports = connectDb;

Pro Tip: Initialize the Connection on App Startup #

To avoid waiting for the connection in every module, initialize it once when your app starts. For example, in your main app.js:

const connectDb = require('./your-db-file');
const express = require('express');
const app = express();

async function startServer() {
  // Wait for the database connection to be ready first
  await connectDb();
  
  // Start your server only after the database is connected
  app.listen(3000, () => {
    console.log('Server running on port 3000, database connected');
  });
}

// Handle startup errors
startServer().catch(err => {
  console.error('Failed to start app:', err);
  process.exit(1);
});

All these solutions ensure that your code only uses the database instance after the asynchronous connection has been established, eliminating the undefined issue.

内容的提问来源于stack exchange，提问作者Willem van der Veen