You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello all (to anyone still actively using sequelize-auto-migrations). To all who have contributed PRs over the years - THANK YOU! Your PR is not in vain. Hence, we've created a fork that we're actively maintaining.
The new npm name is sequelize-lazy-migrations and you can install it via that name:
npm install --save-dev sequelize-lazy-migrations
Plans
Add a baseline unit test coverage
Merge as many PR contributions as possible (anything without breaking changes will be considered)
Fix high priority bugs (e.g. phantom migrations being generated due to validations)
Why?
My company is still actively utilizing and relying on this library. Requests to add contributors have gone unanswered. Hence this was the best course of action.
The text was updated successfully, but these errors were encountered:
I'm trying to use the features for the first time because I'm kind of new to Sequelize (I was a TypeORM boy and now I'm trying to use sequelize in a new project at work).
I found that fork through this StackOverflow answer which has some PR links about why the owner of the fork has created it.
So I guess it could be useful for your purpose to know this other fork, and in my case perhaps I might go back to TypeORM.
What
Hello all (to anyone still actively using
sequelize-auto-migrations
). To all who have contributed PRs over the years - THANK YOU! Your PR is not in vain. Hence, we've created a fork that we're actively maintaining.It's available here:
https://github.com/matmar10/sequelize-lazy-migrations
The new npm name is
sequelize-lazy-migrations
and you can install it via that name:Plans
Why?
My company is still actively utilizing and relying on this library. Requests to add contributors have gone unanswered. Hence this was the best course of action.
The text was updated successfully, but these errors were encountered: