typeorm: [question] migration cannot recongnize keyword `import`?

Had same problem, solved by having: "migrate": "ts-node ./node_modules/.bin/typeorm migrations:generate" in the scripts section of package.json and then doing: npm run migrate -- --name InitialMigration

I agree. You need to use ts-node. The problem for me is both ./node_modules/.bin/typeorm and ./node_modules/.bin/typeorm.cmd fail to generate/run/revert the migrations. I can create an empty migration using typeorm migrations:create without any issues.

My work-around is accessing the typeorm cli.js directly using package json, like so… "migrations:generate": "ts-node ./node_modules/typeorm/cli.js migrations:generate", "migrations:run": "ts-node ./node_modules/typeorm/cli.js migrations:run", "migrations:revert": "ts-node ./node_modules/typeorm/cli.js migrations:revert" Then running the migrations like so… yarn migrations:generate --name BaseMigration yarn migrations:run yarn migrations:revert This is working for me on Windows10, using VSCode and git-bash terminal. I am enjoying working with TypeORM, I like it.

You can execute any node app using ts-node:

ts-node ./node_modules/.bin/typeorm

This way it will compile ts files on the fly.

This should be part of ts-node documentation, but yeah its good to mention about it in typeorm documentation too.

@martinsura this worked for me. Added script in package.json "migrate": "ts-node ./node_modules/typeorm/cli.js migrations:generate" Then generated migration like so… yarn migrate -- --name BaseMigration

If I use "migration:generate": "ts-node ./node_modules/typeorm/cli.js migration:generate" in package.json I get the error message “missing argument n”.

These scripts are working for me:

  "migration:generate": "ts-node ./node_modules/typeorm/cli.js migration:generate -n",

  "migration:run": "ts-node ./node_modules/typeorm/cli.js migration:run",

  "migration:revert": "ts-node ./node_modules/typeorm/cli.js migration:revert"

Then in commandline: npm run migration:generate MigrationName

For anyone else having issues using ts-node in yarn workspaces or lerna. Just make a file called tsnode-typeorm.js:

require('ts-node').register({ typeCheck: false });
require('typeorm/cli');

To run migrations run node tsnode-typeorm migrations:run

Guys to summarize, TypeORM uses TypeScript to enhance javascript and enable a better way of declaring your schema, however it doesn’t give you TS to JS compilation nor a middleware for it’s execution directly in TS, so when you execute TypeORM, you NEED to use ts-node by prepending it to all commands used in console (though it’s easier to hard code such commands in npm scripts in package.json).

About @gmongin issue, the following line is a bash command, i doubt it would work in windows cmd or powershell, maybe try installing git-bash, babun (i like it, but some issues with yarn in the most recent version), or some other bash emulator:

basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")

Lastly i know packages which accept TS files, like Gulp, they accept their config file to be made in TS, and they will tap into ts-node if installed, i asked before if that can be done here as well, but most people said it’s not a priority, and prepending the TypeORM command with ts-node is a good enough workaround, what a shame, i feel that most newcomers bump into this and creates a high barrier of entry.

I agree. You need to use ts-node. The problem for me is both ./node_modules/.bin/typeorm and ./node_modules/.bin/typeorm.cmd fail to generate/run/revert the migrations. I can create an empty migration using typeorm migrations:create without any issues.

My work-around is accessing the typeorm cli.js directly using package json, like so… "migrations:generate": "ts-node ./node_modules/typeorm/cli.js migrations:generate", "migrations:run": "ts-node ./node_modules/typeorm/cli.js migrations:run", "migrations:revert": "ts-node ./node_modules/typeorm/cli.js migrations:revert" Then running the migrations like so… yarn migrations:generate --name BaseMigration yarn migrations:run yarn migrations:revert This is working for me on Windows10, using VSCode and git-bash terminal. I am enjoying working with TypeORM, I like it.

Just want to help others who also looked into this solution, now the migration commands are Singular, eg: "migration:generate": "ts-node ./node_modules/typeorm/cli.js migration:generate",

typeorm Version I am using: “~0.2.7”

try to run js files instead of ts, e.g.:

    "migrations": [
        "src/models/migrations/*.js" // make sure to specify outdir if you are using outdir
    ]

“missing argument n”

Oh my goodness, if anyone else ever comes across this thread, and has the error message: “Missing required argument: n”

After running a command like this:

npm run typeorm:cli -- migration:create -n UserFullName

The issue was PowerShell!

Look in the screenshot above how it’s removed the -n flag on the command

Switching to cmd or Git Bash solved this for me.

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…

@aluco100 migration generation is supported only in mysql right now, we are planning to release its support in sqlite in 0.2.0