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
Found a strange bug today, if nodemon is running, the knex migrations will sometimes fail and output 'Already up to date' even if there are new migrations. Here is a StackOverflow threadabout the issue.
Two possible solutions: make it clear in the readme that the start:dev script can't be running while running the migrations, or add --ignore src/db/migrations to the start-dev script (or a nodemon.json file with the same option set).
The text was updated successfully, but these errors were encountered:
Found a strange bug today, if nodemon is running, the knex migrations will sometimes fail and output 'Already up to date' even if there are new migrations. Here is a StackOverflow threadabout the issue.
Two possible solutions: make it clear in the readme that the
start:dev
script can't be running while running the migrations, or add--ignore src/db/migrations
to thestart-dev
script (or a nodemon.json file with the same option set).The text was updated successfully, but these errors were encountered: