Got the same error in conjunction NextJS + MongoDB + Typegoose. Locally it works fine but after deploying on Vercel (or netlify) got the wrong behavior. Depending on the scenario it cause the amount of newly appeared collections. To solve this I force to set collection names in @modelOptions. F.e.

@modelOptions({schemaOptions: { timestamps: true, collection: 'ships'}})
export class Ship {
...
}

Docs: https://typegoose.github.io/typegoose/docs/guides/advanced/models-with-same-name/