Last modified: Mon Mar 02 2020 07:15:13 GMT+0000 (Coordinated Universal Time)
Connection and installation
npm install mongoose
// or
yarn add mongoose
Connection
mongoose
.connect( < DATABASE_COLLECTION_STRING > , {
useNewUrlParser: true,
useUnifiedTopology: true
})
.then(() => console.log("Database connected"))
.catch(e => console.log("Error connecting db", e.message))
Connection events
Listen for error events on the connection.
mongoose.connection.on(<EVENT_TYPE>, msg => {
// msg
})
Connection Events
connecting: Emitted when Mongoose starts making its initial connection to the MongoDB serverconnected: Emitted when Mongoose successfully makes its initial connection to the MongoDB serveropen: Equivalent toconnecteddisconnecting: Your app calledConnection#close()to disconnect from MongoDBdisconnected: Emitted when Mongoose lost connection to the MongoDB server. This event may be due to your code explicitly closing the connection, the database server crashing, or network connectivity issues.close: Emitted afterConnection#close()successfully closes the connection. If you callconn.close(), you'll get both a 'disconnected' event and a 'close' event.reconnected: Emitted if Mongoose lost connectivity to MongoDB and successfully reconnected. Mongoose attempts to automatically reconnect when it loses connection to the database.error: Emitted if an error occurs on a connection, like aparseErrordue to malformed data or a payload larger than 16MB.fullsetup: Emitted when you're connecting to a replica set and Mongoose has successfully connected to the primary and at least one secondary.all: Emitted when you're connecting to a replica set and Mongoose has successfully connected to all servers specified in your connection string.reconnectFailed: Emitted when you're connected to a standalone server and Mongoose has run out ofreconnectTries. The MongoDB driver will no longer attempt to reconnect after this event is emitted. This event will never be emitted if you're connected to a replica set.