Is this a fix to this issue?
I tested
"mongodb/laravel-mongodb": "5.0.x-dev"

Got this error in laravel breeze starter,
run php artisan test

</details>

If the issue above is unrelated to this PR let me know I will delete this, sorry for polluting comments here
Sorry the solution was very simple just add this in Service Provider

MongoDB\Laravel\Auth\PasswordResetServiceProvider::class,

the solution was very simple just add this in Service Provider

MongoDB\Laravel\Auth\PasswordResetServiceProvider::class,

Your issue could have been avoided by automatically converting UTCDateTime to DateTimeImmutable objects in query results. That way, the custom DatabaseTokenRepository would become useless. I haven't do that at first, because it rases opinionated choices (class Carbon or DateTime, immutability, timezone).

the solution was very simple just add this in Service Provider
MongoDB\Laravel\Auth\PasswordResetServiceProvider::class,

Your issue could have been avoided by automatically converting UTCDateTime to DateTimeImmutable objects in query results. That way, the custom DatabaseTokenRepository would become useless. I haven't do that at first, because it rases opinionated choices (class Carbon or DateTime, immutability, timezone).

That would have been nice. You do what's best. Just my opinion it might be better if in docs there is quick section for FAQ or cheatsheet that is not by default supported by laravel mongodb and need to use a Custom Provider. Just minor improvement so people that are already familiar can jump straight to it hehe, but then again the documentation is great

I decided not convert dates in results for now. Tracking in PHPORM-234