NestJS, PortsgreSQL and TypeORM - Migrations not running properly

Question

When trying to run the TypeORM Migrations, either automatically in the application startup or manually via the TypeORM CLI, only the migrations table gets created (and it stays empty). The migration files themselves are not being executed.

Here is my tsconfig.json

{
  "compilerOptions": {
    "module": "commonjs",
    "declaration": true,
    "removeComments": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "target": "es2017",
    "sourceMap": true,
    "outDir": "./dist",
    "baseUrl": "./",
    "incremental": true
  }
}

Here is my package.json

...
"typeorm": "node --require ts-node/register ./node_modules/typeorm/cli.js",
...

Here is my ormconfig.json

...
"entities": ["dist/**/*.entity{.ts,.js}"],
"synchronize": true,
"migrationsRun": true,
"migrations ": ["dist/migrations/*{.ts,.js}"],
"cli": {
    "migrationsDir": "src/migrations"
  }
...

The migration files are being created through the TypeORM CLI and they are to populate some tables (insert statements). They are not related to changes in the database schema.

Please, can anyone help me make it work?

I tried it but the only thing that happens is that the migrations table gets created (if it's not yet created). It's as if the migration files I created with the insert statements are not being found. I checked "migrations": ["dist/migrations/*{.ts,.js}"]and the files (.ts and .js) are all there. — Felipe Calderano

Felipe Calderano Felipe Calderano · Accepted Answer · 2020-08-25T19:11:21

That was a silly one! I guess some times the simplest problems are the hardest to spot.

The problem was in the ormconfig.json file. I removed this empty space ("migrations ":) and everything worked just fine.

NestJS, PortsgreSQL and TypeORM - Migrations not running properly

2 Answers