Check out my personal website that I created using NextJS and hosted on Vercel. The site connects to a MongoDB database through Mongoose in my NodeJS API.
Recently, I've been encountering a strange error affecting only about 1% of the users:
MongooseError: Cannot call 'hotels.aggregate()' before initial connection is complete if 'bufferCommands = false'. Make sure you 'await mongoose.connect()' if you have 'bufferCommands = false'.
at NativeCollection.<computed> [as aggregate] (/var/task/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:193:15)
at /var/task/node_modules/mongoose/lib/aggregate.js:998:18
at /var/task/node_modules/kareem/index.js:23:7
at processTicksAndRejections (internal/process/task_queues.js:77:11)
(hotels represents the collection being displayed, with the .aggregate() function being called within my API)
I am unable to consistently replicate this error, although it has happened to me as well.
I'm adhering to the recommended method from NextJS for connecting to MongoDB by referring to their example code snippet:
import mongoose from 'mongoose'
const MONGODB_URI = process.env.MONGODB_URI
// Code snippets continue...
Despite following the correct structure, the issue persists. Here's how my API starts:
import dbConnect from "utils/dbConnect";
import HotelModel from "models/HotelModel";
export default async function handler(req, res) {
await dbConnect();
try {
const pipeline = {}; // this is a big aggregation pipeline
const hotels = await HotelModel.aggregate(pipeline);
return res.status(200).json(hotels);
} catch{
...
}
}
Any suggestions on what might be causing this unexpected behavior?