-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
_id no longer recursive when another version of bson in installed #15140
Comments
Can you please provide some code samples that demonstrate this issue? |
Attached is a simple project which creates a document in db, finds it, then logs doc._id._id steps to reproduce the bug : yarn install
# logs an _id
yarn start
yarn add bson@6.1.0
# logs undefined
yarn start
yarn add bson@6.10.1
# logs an _id
yarn start |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days |
@vkarpov15 do you think this is a mongoose bug ? or the issue should be closed ? |
Sorry for letting this issue get stale, we'll review this next week. |
Prerequisites
Mongoose version
8.9.1
Node.js version
20.7.0
MongoDB server version
8.0.1
Typescript version (if applicable)
No response
Description
I experienced something quite similar to this closed issue #14867
Following a mongoose update (8.9.1) in my project (with yarn) without any problem, for whatever reason I decided to delete the yarn.lock file to regenerate it, and encountered the issue described by @gl-aagostino
The recursiveness worked when creating an ObjectId in code, but fails when loading a document from the db
Turns out this version of mongoose uses bson@6.10.1, and bson@6.1.0 was also in my package.json
Updating bson to 6.10.1 resolved the problem
Not sure if it's a yarn, mongoose or bson issue, but couldn't find talks about this anywhere else
Steps to Reproduce
create a project with mongoose@8.9.1 and bson@6.1.0
insert a doc in db and find it
doc._id._id should crash
Expected Behavior
doc._id._id should not crash
The text was updated successfully, but these errors were encountered: