Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NEW MAINTAINER - active fork, new repo name, & plans #90

Open
matmar10 opened this issue Aug 5, 2021 · 3 comments
Open

NEW MAINTAINER - active fork, new repo name, & plans #90

matmar10 opened this issue Aug 5, 2021 · 3 comments

Comments

@matmar10
Copy link

matmar10 commented Aug 5, 2021

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:

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.

@bigLucas
Copy link

@matmar10 did you check this fork: https://github.com/Scimonster/sequelize-auto-migrations?

FYI this other fork has some other features that your fork does not have.

@matmar10
Copy link
Author

Thanks @bigLucas! Are you using the features in that fork? We could merge them in at sequelize-lazy-migrations if so.

@bigLucas
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants