typeorm: Migration Unexpected token error

I solved my problem by installing ts-node as a dev dependency:

npm i -D ts-node

and later by adding script to package.json file:

{
  /* ... */
  "scripts": {
    /* ... */
    "typeorm": "ts-node ./node_modules/.bin/typeorm"
  }
}

Now you can invoke any typeorm CLI command in the following way:

npm run typeorm -- migration:generate -n MigrationName

Guys, I believe this problem happen when typeorm migration:run tries to execute .ts files. Try to change your ormconfig and specify only .js files in there.

I solved my problem by installing ts-node as a dev dependency:

npm i -D ts-node

and later by adding script to package.json file:

{
  /* ... */
  "scripts": {
    /* ... */
    "typeorm": "ts-node ./node_modules/.bin/typeorm"
  }
}

Now you can invoke any typeorm CLI command in the following way:

npm run typeorm -- migration:generate -n MigrationName

I tried that and even changed the script to mine that was working (ts-node ./node_modules/typeorm/cli.js) and typed npm run typeorm with no lock. the scipt it tries to run is ts-node ./node_modules/typeorm/cli.js "migration:generate" "-n" "MigrationName" why put them in quotations ???

Update: solved by removing "esModuleInterop": true, from tsconfig but still, I have to put all script in scripts section I mean npm run typeorm -- migration:generate -n MigrationName translated to ts-node ./node_modules/typeorm/cli.js "migration:generate" "-n" "MigrationName" thanks

I’m using migration with .ts files and it works without any problems.

// package.json->scripts
"db:migrate": "npx ts-node ./node_modules/.bin/typeorm migration:run -f ormconfig-cli",

// ormconfig-cli.ts
import { SnakeNamingStrategy } from './src/database/snake-naming.strategy';

module.exports = {
   type: 'mysql',
   host: 'localhost',
   port: 3306,
   username: 'root',
   password: '123456789',
   database: 'mydb',
   synchronize: false,
   logging: true,
   maxQueryExecutionTime: 100,
   namingStrategy: new SnakeNamingStrategy(),
   entities: ['src/database/entity/**/*.ts'],
   migrations: ['src/database/migration/**/*.ts'],
   subscribers: ['src/database/subscriber/**/*.ts'],
   cli: {
      entitiesDir: 'src/database/entity',
      migrationsDir: 'src/database/migration',
      subscribersDir: 'src/database/subscriber'
   }
};

after long I installed ts-node typescript typeorm globally and use ts-node ./node_modules/typeorm/cli.js migration:generate -n new1 command things start to work. Update: I added "esModuleInterop": true, to tsconfig.json

I solved my problem by installing ts-node as a dev dependency:

npm i -D ts-node

and later by adding script to package.json file:

{
  /* ... */
  "scripts": {
    /* ... */
    "typeorm": "ts-node ./node_modules/.bin/typeorm"
  }
}

Now you can invoke any typeorm CLI command in the following way:

npm run typeorm -- migration:generate -n MigrationName

I tried that and even changed the script to mine that was working (ts-node ./node_modules/typeorm/cli.js) and typed npm run typeorm with no lock. the scipt it tries to run is ts-node ./node_modules/typeorm/cli.js "migration:generate" "-n" "MigrationName" why put them in quotations ???

Update: solved by removing "esModuleInterop": true, from tsconfig but still, I have to put all script in scripts section I mean npm run typeorm -- migration:generate -n MigrationName translated to ts-node ./node_modules/typeorm/cli.js "migration:generate" "-n" "MigrationName" thanks

.\node_modules\.bin\ts-node ./node_modules/typeorm/cli.js migration:generate -n MigrationName worked for me. I’ve installed ts-node locally.