Alyx

This seems to be a feature request for sequelize rather than sequelize-typescript, consider opening one in [our repository](https://github.com/sequelize/sequelize/) instead

Use the `logging` option to find out what the SQL looks like, it looks like the table name is not 'projects' in the SQL sequelize generates

This has actually been improved recently in Sequelize, and can be used in sequelize-typescript too, see `InferAttributes` & `InferCreationAttributes` here https://sequelize.org/docs/v6/other-topics/typescript/ It should get even better in a future major...

The problem you're experiencing (it's been a couple months so I hope you found a resolution since then) is the same as this one: https://github.com/RobinBuschmann/sequelize-typescript/issues/778

`@sequelize/core` is Sequelize 7, you need to use `sequelize` with Sequelize-TypeScript for now `Op.match` can be used like this: ```typescript import { Op } from 'sequelize'; User.findAll({ where: { name:...

Take a look at the updated sequelize documentation regarding the issue with class fields: https://sequelize.org/v6/manual/model-basics.html#caveat-with-public-class-fields

The fact that babel still emits public class fields tagged with `declare` when using decorators is problematic. Makes sequelize/sequelize#14300 all the more pressing.

This is something we plan on improving in Sequelize itself (See 'Model Inheritance' here https://github.com/sequelize/sequelize/issues/14298)

This change has been reverted in v6 but it's still landing in v7 I'm not sure what the alias-inference logic does but if it makes sense to have it upstream,...

What do you mean? The change has already been reverted