Properties with unknown type in the mongoose model when set timestamps to true in v6.8.0

[Code-Mythos]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the bug has not already been reported

Mongoose version

6.8.0

Node.js version

16.15.1

MongoDB server version

6.0

Typescript version (if applicable)

4.9.4

Description

In version 6.8.0, when I set the timestamps option to true in a schema, the created model has properties with unknown types that will cause a lot of problems in implementing the application. However, when I switch back to version 6.7.5 the problem disappears.

Version 6.8.0:

(property) Users: Model<{
    createdAt: NativeDate;
    updatedAt: NativeDate;
} & {
    email?: unknown;
    password?: unknown;
    name?: unknown;
}, {}, {
    // This is a custom method in the schema
    comparePassword: (this: Document<unknown, any, FlatRecord<{
        email: string;
        password: string;
        name: string;
...

When switched back to version 6.7.5 without any modification:

(property) Users: Model<{
    email: string;
    password: string;
    name: string;
}, {}, {
    // This is a custom method in the schema
    comparePassword: (this: Document<unknown, any, FlatRecord<{
        email: string;
        password: string;
        name: string;
...

Steps to Reproduce

Considering you are using typescript:

1. Install version 6.8.0 : npm i mongoose@6.8.0
2. Create a schema with some properties and set the timestamps option to true.
3. Create a connection using mongoose.createConnection.
4. Create a model for the schema using the connection.model.
5. Hover over the created model to see the type of the model.

const userSchema = new Schema(
  {
    email: {
      type: String,
      required: true,
    },

    password: {
      type: String,
      required: true,
    },
    name: {
      type: String,
      required: true,
    },
  },
  {
    methods: {
      comparePassword: function (candidatePassword: string): Promise<boolean> {
        const user = this;

        return new Promise((resolve, reject) => {
          compare(candidatePassword, user.password, (err, isMatch) => {
            if (err) return reject(err);

            return resolve(isMatch);
          });
        });
      },
    },

    timestamps: true,
  }
);

const connection = createConnection(config.authDatabaseURL);

const Models = {
  Users: connection.model("users", userSchema),
};

Expected Behavior

(property) Users: Model<{
    createdAt: NativeDate;
    updatedAt: NativeDate;
} & {
    email: string;
    password: string;
    name: string;
}, {}, {
    // This is a custom method in the schema
    comparePassword: (this: Document<unknown, any, FlatRecord<{
        email: string;
        password: string;
        name: string;
...

Or:

(property) Users: Model<{
    email: string;
    password: string;
    name: string;
}, {}, {
    // This is a custom method in the schema
    comparePassword: (this: Document<unknown, any, FlatRecord<{
        email: string;
        password: string;
        name: string;
...

[IslandRhythms]

import { Schema, model, connect, connection, createConnection } from 'mongoose';

// 1. Create an interface representing a document in MongoDB.
interface IUser {
  name: string;
  email: string;
  avatar?: string;
}

// 2. Create a Schema corresponding to the document interface.
const userSchema = new Schema<IUser>({
  name: { type: String, required: true },
  email: { type: String, required: true },
  avatar: String
}, { timestamps: true });

// 3. Create a Model.
// const User = model<IUser>('User', userSchema);

run().catch(err => console.log(err));

async function run() {
  // 4. Connect to MongoDB
  await createConnection('mongodb://localhost:27017/test');
  const User = connection.model<IUser>("User", userSchema);

  const user = new User({
    name: 'Bill',
    email: 'bill@initech.com',
    avatar: 'https://i.imgur.com/dM7Thhn.png'
  });
  await user.save();

  console.log(user.email); // 'bill@initech.com'
}

[Code-Mythos]

Please try the following to reproduce the issue:

const userSchema = new Schema(
  {
    email: {
      type: String,
      required: true,
    },

    password: {
      type: String,
      required: true,
    },
    name: {
      type: String,
      required: true,
    },
  },
  {
    methods: {
      comparePassword: function (candidatePassword: string): Promise<boolean> {
        const user = this;

        return new Promise((resolve, reject) => {
          compare(candidatePassword, user.password, (err, isMatch) => {
            if (err) return reject(err);

            return resolve(isMatch);
          });
        });
      },
    },

    timestamps: true,
  }
);

const connection = createConnection(config.authDatabaseURL);

const Models = {
  Users: connection.model("users", userSchema),
};

[IslandRhythms]

no change

[Code-Mythos]

I've attached an image to my previous comment.
When you create a user by defining all its required fields it's obvious that there will not be an error.
*** Please hover over "Users" in the Models object. ***

Further:
Consider when you found a user using the findOne method and then you are trying to use the comparePassword method:

          const user = await Db.Users.findOne({ email });

          if (!user) throw new Error(`User not found: ${email}`);

          // Ignore typescript error
          const isPasswordValid: boolean = await user.comparePassword(password);

          if (!isPasswordValid) throw new Error(`Invalid password: ${email}`);

          // Any object returned will be saved in `user` property of the JWT
          const userObject: User = {
            id: user._id.toString(),
            name: user.name,
            email: user.email,
          };

          return userObject;

[IslandRhythms]

My b

[Code-Mythos]

When you switch back to v6.7.5 the problem disappears.
I do not know what happens to the type definitions in v6.8.0 when the timestamps option is set to true.
Thank you for your follow-up.