Migration cli unexpected token import #371

adithep · 2017-03-26T05:12:00Z

I wrote everything in typescript.
The application and everything work fine, but as soon as I call

typeorm migrations:run

I get this error

src/entity/User.ts:1
(function (exports, require, module, __filename, __dirname) { import {Entity, Column, PrimaryGeneratedColumn} from "typeorm";
^^^^^^
SyntaxError: Unexpected token import
at Object.exports.runInThisContext (vm.js:78:16)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Function.PlatformTools.load (/usr/local/lib/node_modules/typeorm/platform/PlatformTools.js:26:20)
at /usr/local/lib/node_modules/typeorm/util/DirectoryExportedClassesLoader.js:29:69
(node:38469) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): SyntaxError: Unexpected token import
(node:38469) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Not sure if it matters but this is my tsconfig.json:

{
"compilerOptions": {
"declaration": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"isolatedModules": false,
"module": "commonjs",
"moduleResolution": "node",
"outDir": "dist",
"sourceMap": true,
"sourceRoot": "src",
"noEmitHelpers": false,
"target": "es5",
"typeRoots": [
"node_modules/@types"
],
"lib": ["es6", "dom"]
},
"exclude": [
"node_modules"
]
}

What ever I change in tsconfig.json seems to not effect the error at all.

The text was updated successfully, but these errors were encountered:

pleerock · 2017-03-28T16:38:29Z

you node environment tries to load src/entity/User.ts, but it should load .js. So you either need to run app with ts-node, or set proper configuration for JS FILES in your ormconfig cli section, e.g. dist/migrations/.*js

pleerock · 2017-04-01T11:08:34Z

did you resolve your issue?

adithep · 2017-04-03T13:32:54Z

Yes. Thankyou.

…

On Sat, Apr 1, 2017 at 6:08 PM, Umed Khudoiberdiev ***@***.*** > wrote: did you resolve your issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#371 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF_TKcft41bhrW4f-mWjrq-DFLsynzyiks5rrjA0gaJpZM4MpUiq> .

SaeedSyedAli96 · 2017-12-13T08:01:25Z

@adithep how did you resolve the issue?

stormpat · 2018-01-20T10:27:30Z

Anyone wondering about this, you must run your .ts files thru ts-node first.

Simply:

>> ./node_modules/.bin/ts-node ./node_modules/.bin/typeorm <command>

davidmpaz · 2018-01-22T17:32:56Z

Hi @stormpat,

thanks for the hint. Still is not working for me.

./node_modules/.bin/ts-node ./node_modules/.bin/typeorm schema:log

gives me still:

import { Column, Entity, ManyToOne } from 'typeorm';
^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:607:28)
    at Module.m._compile (/srv/http/is7/mobile-sdk/src/modules/products/node_modules/ts-node/src/index.ts:422:23)
    at Module._extensions..js (module.js:654:10)
    at Object.require.extensions.(anonymous function) [as .ts] (/srv/http/is7/mobile-sdk/src/modules/products/node_modules/ts-node/src/index.ts:425:12)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)

Any idea ?

pleerock · 2018-01-23T06:11:25Z

@davidmpaz try to setup your tsconfig properly - try to set target to es5

davidmpaz · 2018-01-23T09:19:50Z

Hi @pleerock ,

thanks for answering. These are my current config files

tsconfig.json:

{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "skipLibCheck": true,
    "noStrictGenericChecks": true,
    "lib": [
      "dom",
      "es2015"
    ],
    "module": "es2015",
    "moduleResolution": "node",
    "sourceMap": true,
    "target": "es5"
  },
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "node_modules"
  ],
  "compileOnSave": false,
  "atom": {
    "rewriteTsconfig": false
  }
}

ormconfig.json

{
    "type": "sqlite",
    "database": "./products.db",
    "synchronize": true,
    "logging": false,
    "entities": [
        "src/models/**/*.ts"
    ],
    "migrations": [
        "src/migration/**/*.ts"
    ],
    "subscribers": [
        "src/subscriber/**/*.ts"
    ],
    "cli": {
        "entitiesDir": "src/models",
        "migrationsDir": "src/migration",
        "subscribersDir": "src/subscriber"
    }
}

package.json deps:

"dependencies": {
        "@angular/common": "4.1.3",
        "@angular/core": "4.1.3",
        "@angular/forms": "4.1.3",
        "@angular/http": "4.1.3",
        "ionic-angular": "^3.6.0",
        "typeorm": "0.1.11",
        "reflect-metadata": "^0.1.10",
        "ngx-order-pipe": "^1.1.0",
        "sqlite3": "3.1.13",
        "rxjs": "5.4.0"
    },
    "devDependencies": {
        "tslint": "^5.8.0",
        "tslint-eslint-rules": "^4.1.1",
        "ts-node": "4.1.0",
        "typescript": "^2.6.1"
    }

I would like to see what get generated with my current entity models definitions, was trying to do 'insitu'. I guess I will try to generate a project from scratch and copy paste entities.

But would be nice if I can get it up running in my existent project.

thanks in advance for your time,
David

davidmpaz · 2018-01-23T10:36:01Z

It seems my problem is known here, related to my settings: "module": "es2015"

Sorry to introduce this noise.

Thanks!!

91debug · 2018-01-25T10:54:26Z

@davidmpaz how did you resolve the issue?

These are my current config files
tsconfig.json:

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es5",
    "rootDir": "./",
    "outDir": "./tsc",
    "noImplicitAny": false,
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "moduleResolution": "node",
    "declaration": false,
    "listFiles": false,
    "lib": [
      "es6",
      "dom",
      "es2015.promise",
      "esnext.asynciterable"
    ],
    "noUnusedLocals": true,
  },
  "exclude": [
    ".vscode",
    ".serverless",
    ".git",
    "node_modules"
  ],
  "compileOnSave": true,
  "buildOnSave": false
}

davidmpaz · 2018-01-25T11:01:34Z

@91debug currently I haven't.

91debug · 2018-01-25T11:29:46Z

@davidmpaz i resolved! thank you

davidmpaz · 2018-01-25T12:01:49Z

@91debug, could you share ? :)

91debug · 2018-01-25T12:44:49Z

@davidmpaz

I used this command
./node_modules/.bin/ts-node ./node_modules/.bin/typeorm schema:sync

tonyxiao · 2018-02-15T19:45:08Z

it's surprising that typeorm cli doesn't work with typescript by default without asking user to explicitly pass through ts-node. Is that something which could be built in given how typeorm itself is written in typescript?

SaeedSyedAli96 · 2018-02-16T05:05:17Z

I found a way to make migratons work with my ionic 3 application.
NO NEED TO EXPLICITLY PASS TS-NODE
In ormconfig.json:

{
    "cli": {
        "migrationsDir": "src/migrations/"
    }
}

and the connection:

 await createConnection({
            type: 'cordova',
            database: 'test',
            location: 'default',
            logging: ['error', 'query', 'schema'],
            synchronize: false,
            entities: [
                //entities
            ],
            migrations:[
                //migrations generated by typeorm cli
            ],
            migrationsRun: true
        }).catch(err => console.log("error: ", err));

tsconfig.json

{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [
      "dom",
      "es2015"
    ],
    "module": "es2015",
    "moduleResolution": "node",
    "sourceMap": true,
    "target": "es5",
    "typeRoots": [
      "./node_modules/@types"
    ]
  },
  "include": [
    "src/**/*.ts"
  ],
  "exclude": [
    "node_modules",
    "src/**/*.spec.ts",
    "src/**/__tests__/*.ts"
  ],
  "compileOnSave": false,
  "atom": {
    "rewriteTsconfig": false
  }
}

tonyxiao · 2018-02-17T02:15:23Z

@SaeedSyedAli96 how does it work?

SaeedSyedAli96 · 2018-02-21T05:04:55Z

@tonyxiao I just used migration cli to generate migrations as it needs timestamp. Else Entitites and and other stuff I did manually. I was having issues in running migration from cli but then I got to know that there is an option of migrationsRun as well.

mindonline · 2018-02-27T14:48:37Z

Also, in Win 10 works:
ts-node node_modules\typeorm\cli.js

eightHundreds · 2018-05-03T06:51:21Z

for es project in win 10

.\node_modules\.bin\babel-node .\node_modules\typeorm\cli.js schema:sync

bennycode · 2018-12-03T21:11:08Z

I had a similar issue when running my JavaScript application code (which has been transpiled from TypeScript):

(function (exports, require, module, __filename, __dirname) { import {Column, Entity, PrimaryGeneratedColumn} from "typeorm";

SyntaxError: Unexpected token {

I solved it by pointing the entities in my ormconfig.js to my compiled JavaScript code. Before that (when I had the error) they have been linked to my TypeScript source code.

This configuration now works for me:

ormconfig.js

const ConnectionOptions = {
  cli: {
    entitiesDir: 'src/main/entity',
    migrationsDir: 'src/migration',
    subscribersDir: 'src/subscriber',
  },
  database: 'database/development.db3',
  entities: ['dist/entity/*.js'],
  logging: false,
  migrations: ['src/migration/**/*.ts'],
  subscribers: ['src/subscriber/**/*.ts'],
  synchronize: true,
  type: 'sqlite',
};

if (process.env.NODE_ENV === 'production') {
  ConnectionOptions.database = 'database/production.db3';
}

if (process.env.NODE_ENV === 'test') {
  ConnectionOptions.database = 'database/test.db3';
}

module.exports = ConnectionOptions;

AhmadDeel · 2018-12-24T11:43:30Z

after long I installed ts-node and typescript globally and use
ts-node ./node_modules/typeorm/cli.js migration:generate -n MigrationName command things start to work.
then added these to package.json

{
  /* ... */
  "scripts": {
  /* ... */
    "typeorm-migration-generate": "ts-node ./node_modules/typeorm/cli.js migration:generate -n MigrationName",
    "typeorm-migration-run": "ts-node ./node_modules/typeorm/cli.js migration:run",
    "typeorm-migration-revert": "ts-node ./node_modules/typeorm/cli.js migration:revert"
  }
}

now i can just run npm run typeorm-migration-run and others

2234839 · 2019-03-21T07:54:38Z

"entities": [
      "src/entity/**/*.ts"
   ],
   "migrations": [
      "src/migration/**/*.ts"
   ],
   "subscribers": [
      "src/subscriber/**/*.ts"
   ],

我遇到了同样的问题在将 ormconfig.json中的 ts 改为 js之后解决了问题

vngrv · 2019-09-05T09:01:40Z

It seems my problem is known here, related to my settings: "module": "es2015"

Sorry to introduce this noise.

Thanks!!

this changes killed my build.

rpmonteiro · 2019-09-10T10:29:51Z

Using ENV variables, the fix for me was

TYPEORM_ENTITIES=dist/**/*.entity.js
TYPEORM_MIGRATIONS=dist/migration/*.js
TYPEORM_MIGRATIONS_DIR=dist/migration

Hope this helps someone

willianfalbo · 2020-01-21T20:49:44Z

If you are using ormconfig.json file, it should look like:

{
    "type": "postgres",
    "host": "localhost",
    "port": 5432,
    "username": "root",
    "password": "password",
    "database": "persona_db",
    "entities": [
        "dist/**/*.entity{.ts,.js}"
    ],
    "synchronize": false,
    "migrations": [
        "dist/migrations/**/*{.ts,.js}"
    ],
    "cli": {
        "migrationsDir": "migrations"
    }
}

NOTE: Please refer to the "dist" folder and not the root folder...

zeroliu · 2020-05-29T22:15:38Z

@willianfalbo I ran into a similar issue with deploying the compiled js code to server. I was very confused how any ts file was referenced to the compiled code. Didn't even think about checking ormconfig.json...Thanks so much!!!

gitDylanHub · 2021-06-03T18:52:52Z

Hi @stormpat,

thanks for the hint. Still is not working for me.

./node_modules/.bin/ts-node ./node_modules/.bin/typeorm schema:log

gives me still:

import { Column, Entity, ManyToOne } from 'typeorm';
^^^^^^

SyntaxError: Unexpected token import
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:607:28)
    at Module.m._compile (/srv/http/is7/mobile-sdk/src/modules/products/node_modules/ts-node/src/index.ts:422:23)
    at Module._extensions..js (module.js:654:10)
    at Object.require.extensions.(anonymous function) [as .ts] (/srv/http/is7/mobile-sdk/src/modules/products/node_modules/ts-node/src/index.ts:425:12)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)

Any idea ?
Another workaround for executing the TypeORM from a NPM Scritp.
"typeorm": "node --require ts-node/register ./node_modules/typeorm/cli.js",
"migration:generate": "npm run typeorm migration:generate -- -n",

IgnisDa · 2021-09-02T05:36:59Z

My solution was to install typescript and ts-node globally and use them instead of the node_modules

sudo npm install -g typescript ts-node
ts-node ./node_modules/typeorm/cli.js migration:generate -n FirstMigration

pleerock added the question label Apr 8, 2017

pleerock closed this as completed Apr 8, 2017

wederer mentioned this issue Dec 18, 2018

Note that migrations work with js files only #3276

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Migration cli unexpected token import #371

Migration cli unexpected token import #371

adithep commented Mar 26, 2017 •

edited

Loading

pleerock commented Mar 28, 2017

pleerock commented Apr 1, 2017

adithep commented Apr 3, 2017 via email

SaeedSyedAli96 commented Dec 13, 2017

stormpat commented Jan 20, 2018

davidmpaz commented Jan 22, 2018

pleerock commented Jan 23, 2018

davidmpaz commented Jan 23, 2018

davidmpaz commented Jan 23, 2018

91debug commented Jan 25, 2018 •

edited

Loading

davidmpaz commented Jan 25, 2018

91debug commented Jan 25, 2018

davidmpaz commented Jan 25, 2018

91debug commented Jan 25, 2018

tonyxiao commented Feb 15, 2018

SaeedSyedAli96 commented Feb 16, 2018 •

edited

Loading

tonyxiao commented Feb 17, 2018

SaeedSyedAli96 commented Feb 21, 2018

mindonline commented Feb 27, 2018

eightHundreds commented May 3, 2018 •

edited

Loading

bennycode commented Dec 3, 2018

AhmadDeel commented Dec 24, 2018 •

edited

Loading

2234839 commented Mar 21, 2019 •

edited

Loading

vngrv commented Sep 5, 2019 •

edited

Loading

rpmonteiro commented Sep 10, 2019

willianfalbo commented Jan 21, 2020

zeroliu commented May 29, 2020

gitDylanHub commented Jun 3, 2021

IgnisDa commented Sep 2, 2021

Migration cli unexpected token import #371

Migration cli unexpected token import #371

Comments

adithep commented Mar 26, 2017 • edited Loading

pleerock commented Mar 28, 2017

pleerock commented Apr 1, 2017

adithep commented Apr 3, 2017 via email

SaeedSyedAli96 commented Dec 13, 2017

stormpat commented Jan 20, 2018

davidmpaz commented Jan 22, 2018

pleerock commented Jan 23, 2018

davidmpaz commented Jan 23, 2018

davidmpaz commented Jan 23, 2018

91debug commented Jan 25, 2018 • edited Loading

davidmpaz commented Jan 25, 2018

91debug commented Jan 25, 2018

davidmpaz commented Jan 25, 2018

91debug commented Jan 25, 2018

tonyxiao commented Feb 15, 2018

SaeedSyedAli96 commented Feb 16, 2018 • edited Loading

tonyxiao commented Feb 17, 2018

SaeedSyedAli96 commented Feb 21, 2018

mindonline commented Feb 27, 2018

eightHundreds commented May 3, 2018 • edited Loading

bennycode commented Dec 3, 2018

AhmadDeel commented Dec 24, 2018 • edited Loading

2234839 commented Mar 21, 2019 • edited Loading

vngrv commented Sep 5, 2019 • edited Loading

rpmonteiro commented Sep 10, 2019

willianfalbo commented Jan 21, 2020

zeroliu commented May 29, 2020

gitDylanHub commented Jun 3, 2021

IgnisDa commented Sep 2, 2021

adithep commented Mar 26, 2017 •

edited

Loading

91debug commented Jan 25, 2018 •

edited

Loading

SaeedSyedAli96 commented Feb 16, 2018 •

edited

Loading

eightHundreds commented May 3, 2018 •

edited

Loading

AhmadDeel commented Dec 24, 2018 •

edited

Loading

2234839 commented Mar 21, 2019 •

edited

Loading

vngrv commented Sep 5, 2019 •

edited

Loading