Mongodb adapter: E11000 duplicate key error collection: refresh_tokens index: id_1 dup key: { id: null } about lucia HOT 3 CLOSED

Should be fixed with #32

adapter-mongodb is now deprecated and changed to adapter-mongoose. Now requires the user to set the model/schema by themselves.

Doc: https://lucia-sveltekit.vercel.app/adapters/mongoose

from lucia.

This SO answer says that one can get a duplicate key error on null if the collection has a unique index on that field id, and a doc in that collection doesn't have that field.
This is true. The docs in my refresh_tokens collection do not have a id field on them

from lucia.

Ahh ok, so I checked the indexes on the collection, and mongoose had auto created these indexes:

Now, I'm not sure why it created that id_1 index on the id field, because that isn't even a field in collection?
But I believe it is because, when connecting to mongoose, the autoIndex property is on by default.
So, turning this off should prevent this from happening in future:

const adapter = (url) => {
    const clientPromise = mongoose.connect(url, { autoIndex: false });
    ...

Edit: Can confirm that removing those odd indexes resolves the problem

from lucia.