Skip to content

Not accepting migrations custom path #363

Answered by mmkal
mittalyashu asked this question in Q&A
Discussion options

You must be logged in to vote

@mittalyashu it looks like you're mixing up v2 and v3 syntax. There are some breaking changes in the v3 beta. Please see the note about v2 in the readme. There are a few more changes in the pipeline, likely nothing major/breaking, but if you prefer to stick with v2 until v3 is fully stable, follow the link to the v2.x branch, or npm: https://www.npmjs.com/package/umzug/v/2.3.0

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by mmkal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #363 on November 18, 2020 17:27.