-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency #9900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am running into this error/warnning too. |
A temporarily fix for this is https://stackoverflow.com/a/66102270/10944219 |
This is an issue with the MongoDB driver: mongodb/node-mongodb-native#2734 . We'll upgrade to MongoDB 3.6.5 when it is released 👍 |
Upgrading to version [email protected] has brought this issue to my workspace. However, downgrading back to 5.11.15 fixes it. Also, 5.11.16 brings along a new depreciation warning: |
I can confirm the situation exposed by @Akshit-WTF. Same update and same warning message. I followed the downgrading process proposed in the previous message and the warning disappeared. |
This change has been done due to the last version introduces a warning message that is not documented in the oficial source. This subject is been covered in the next issue Automattic/mongoose#9900
I was getting the same error but after downgrading to v5.11.13 it started working |
Yeah I still get the warning and after tracing the issue here's the result
|
Is the warning on .15 or .16? |
It's an internal issue in mongoose/mongodb drivers
|
yes i know its a internal issue but downgarding to .15 should fix the warning |
Well it doesn't seem to work with version .15 either |
Fixed by #10038 |
Uh oh!
There was an error while loading. Please reload this page.
Upgraded to mongoose 5.11.15, and getting this warnning.
Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency.
Anyone has insights about this one ?
The text was updated successfully, but these errors were encountered: