Issues & Help
Our developer community is vibrant and highly engaged, with extensive experience using Node.js with MongoDB.
Often, the quickest way to get support for general questions is through the MongoDB Community Forums.
Refer to our support channels documentation for more information.
Bugs / Feature Requests
To report a bug or to request a new feature in the Node.js driver, please open a case in our issue management tool, JIRA:
Navigate to the NODE project.
Click Create Issue. Please provide as much information as possible about the issue and the steps to reproduce it.
Bug reports in JIRA for the Node.js driver and the Core Server (i.e. SERVER) project are public.
If you’ve identified a security vulnerability in a driver or any other MongoDB project, please report it according to the instructions found in the Create a Vulnerability Report.
We are happy to accept contributions to help improve the driver.
We will review user contributions to ensure they meet the standards of the codebase.
Pull requests must pass the
travis.ci checks as well as include documentation
To get started check out the source and work on a branch:
git clone https://github.com/mongodb/node-mongodb-native.git cd node-mongodb-native npm install git checkout -b myNewFeature
To run the test suite, you must have a server topology running and provide the URI to the command.
For example, if you have a single server running at
"mongodb://localhost:27017", you can run the following:
MONGODB_URI="mongodb://localhost:27017" npm test
Note that, depending on the type of topology that you are running (standalone, replicaset, etc.), different tests will be run.
There are many tools that can help you with setting up different topologies for local testing. Some examples are mtools and mongo-orchestration.