NPM TypeORM is throwing the error message "Duplicate migrations" when changes are made to a migration file

Question

NPM TypeORM is throwing the error message "Duplicate migrations" when changes are made to a migration file

Recently, I made a modification to an existing table by adding a new column using the command

npm run migration:generate <filename>

.

Unfortunately, I realized later on that I had misspelled the column name and needed to correct it (showComission -> showCommission).

Since this was only in my local environment, I went ahead and updated the column name in the migration file and executed the command npm run migration:run.

However, I encountered a duplicated migration error, which led me to check the log where I found the message concerning the modified export class name as **addShowCommissionToCorporationProfile1643792138368.

The following steps were taken:

- typeorm migration:run

- query: SELECT * FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = 'abc' AND TABLE_NAME = 'migrations'

- query: SELECT * FROM abc.migrations migrations ORDER BY id DESC

Further along, I encountered an error during migration run:
Error: Duplicate migrations: addShowCommissionToCorporationProfile1643792138368
at MigrationExecutor.checkForDuplicateMigrations
at MigrationExecutor.getMigrations
at MigrationExecutor.<anonymous> 
at step 
at Object.next 
at fulfilled 
at processTicksAndRejections npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d2b3b0b1ffb3a2bb92e3fce2fce2">[email protected]</a> migration:run: `typeorm migration:run`
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] migration:run script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

In an attempt to fix the issue, I tried reverting using npm run migration:revert, but faced the same error. I then reverted the migration file back to its original state and created a new migration file specifically for renaming the column using

npm run migration:generate --filename

, yet still encountered the same error. In one final effort to resolve the issue, I deleted the newly created migration file and ran only the original migration file (initial state), however, the error persisted.

I am seeking advice on how to rectify this situation as all I wanted to do was simply rename the column...

If more information or clarification is needed, please feel free to ask.

Your help and guidance are greatly appreciated.

javascript database npm migration typeorm

Answer 1

Answer №1

Encountered a similar issue while working on a NestJS project. The workaround that worked for me was to remove the dist folder, then rebuild the project, allowing me to successfully execute the new migration.

After some recent changes to the project's structure, including relocating the migrations to a different directory, I discovered an odd behavior in Nest. Moving files triggered a partial rebuilding of the project in the destination folder but not in the original location, leading to duplicate migrations. A full rebuild resolved the issue by eliminating the duplicates in the build.

Answer 2

Encountered a similar issue while working on a NestJS project. The workaround that worked for me was to remove the dist folder, then rebuild the project, allowing me to successfully execute the new migration.

After some recent changes to the project's structure, including relocating the migrations to a different directory, I discovered an odd behavior in Nest. Moving files triggered a partial rebuilding of the project in the destination folder but not in the original location, leading to duplicate migrations. A full rebuild resolved the issue by eliminating the duplicates in the build.

Answer 3

Answer №2

I encountered a similar problem and was taken aback by the lack of search results on Google regarding this issue.

I am currently utilizing it for a NestJS application, however, deleting the dist folder and rebuilding (as mentioned in other solutions) did not resolve the issue.

The root cause turned out to be using an index file in the migrations directory that exported the migrations along with the migration files themselves. This caused TypeORM to import the migrations twice - once from the migration file and once from the index file.

In such scenarios, there are 2 possible solutions:

Remove index.ts from the migrations folder
Modify the value of the migrations option in your DataSource configuration to specify the exact path to the index file like path/to/migrations/index.{ts,js} instead of using a regex with wildcards in the filename. Additionally, ensure that new migrations are also added to the index file.

Answer 4

I encountered a similar problem and was taken aback by the lack of search results on Google regarding this issue.

I am currently utilizing it for a NestJS application, however, deleting the dist folder and rebuilding (as mentioned in other solutions) did not resolve the issue.

The root cause turned out to be using an index file in the migrations directory that exported the migrations along with the migration files themselves. This caused TypeORM to import the migrations twice - once from the migration file and once from the index file.

In such scenarios, there are 2 possible solutions:

Remove index.ts from the migrations folder
Modify the value of the migrations option in your DataSource configuration to specify the exact path to the index file like path/to/migrations/index.{ts,js} instead of using a regex with wildcards in the filename. Additionally, ensure that new migrations are also added to the index file.

Answer 5

Answer №3

By running npm run build, I was able to fix the issue at hand.

Answer 6

By running npm run build, I was able to fix the issue at hand.

NPM TypeORM is throwing the error message "Duplicate migrations" when changes are made to a migration file

Answer №1

Answer №2

Answer №3

Similar questions

Revolutionary custom binding with Bootstrap popover integration

Modifying the nodeJS executable path on Windows without administrator privileges

NPM-AUDIT has detected two critical vulnerabilities. What steps should I take next?

How can I retrieve Feature Information exclusively from the currently visible WMS layers in OpenLayers 3?

Is it possible to execute PHP without using Ajax when clicking on a Font Awesome icon?

What methods can be used to modify the behavior of tiptap when pasting plain text?

Tips on eliminating redundant rows while retaining a single one in an Access database

Unresponsive JavaScript on specific element IDs

Configure WebStorm so that node_modules is set as the library root, while simultaneously excluding it from indexing

Does JSON have a special reserved key for identifying the time?

What are the steps to create a class diagram for a NodeJS application?

Obtaining essential data while facing a redirect situation

Storing values in an array when checkboxes are selected within an ng-repeat loop in AngularJS

Troubleshooting issue with Bootstrap slider: CSS display problem

Ways to position divs without causing them to collapse or override existing divs

What is a clever way to monitor the completion of a forEach loop using promises?

Is it possible to implement a Promise.some() function that includes a timeout

A tool that showcases outcomes determined by the interaction of two variables

Fixing a node-gyp error using npm audit fix: A step-by-step guide

Errors have been observed when using JavaScript variables that begin with the symbol $