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, Commented Aug 25, 2020 at 18:42

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

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.

FULL STACK DEV · Accepted Answer · 2020-08-25 18:08:45Z

2

you should have synchronized to false synchronize:false

And from the terminal run

npx typeorm migration:generate -n AnyNameYouWant

After that, you can run

npx typeorm migration:run

You may also have to run nest build before running these commands.

answered Aug 25, 2020 at 18:08

FULL STACK DEV

16k6 gold badges49 silver badges67 bronze badges

1 Comment

Felipe Calderano Over a year ago

I forgot to mention that the migration files I created are to populate some tables (insert statements). They are not related to changes in the database schema... I will edit the question with this info. I tried with synchronize:false but the result was the same.

Milad Ashoori · Accepted Answer · 2022-09-19 10:43:44Z

I think this one is to synchronize the database with the schema, and it's not a good idea. "synchronize": true,

Collectives™ on Stack Overflow

NestJS, PortsgreSQL and TypeORM - Migrations not running properly

3 Answers 3

Comments

1 Comment

Comments

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

Comments

Related