Trying to improve the NestJS + Sequelize developer experience — Feedback wanted
I've been working on a project called **nest-sequelize-repository** that aims to bring a TypeORM-like repository experience to **NestJS + Sequelize**, while still using Sequelize under the hood.
The goal isn't to replace Sequelize or build another ORM. It's simply to reduce boilerplate and provide a reusable, strongly typed abstract repository for common CRUD operations and patterns.
# Current features
* Generic abstract repository
* Type-safe CRUD operations
* Pagination support
* Soft delete support
* Transaction support
* Custom repository extensions
* Better error handling
# Planned roadmap
* Cursor pagination
* More repository helpers and developer experience improvements
I'd really appreciate feedback from people using **NestJS + Sequelize**.
* What repetitive code do you find yourself writing in every repository?
* What's the biggest pain point when working with Sequelize in NestJS?
* Are there any features you'd love to see in a library like this?
Repository: [https://github.com/stbestichhh/nest-sequelize-repository\](https://github.com/stbestichhh/nest-sequelize-repository)
I'd love to hear your thoughts and ideas!