If you have a local typeorm version, make sure it matches the global version we are going to install.
You can install typeorm globally with
npm i -g typeorm. You can also choose to use
npx typeorm <params>for each command if you prefer not having to install it.
You may setup ts-node in your project to ease the operation as follows:
npm install ts-node --save-dev
Add typeorm command under scripts section in package.json
For ESM projects add this instead:
If you want to load more modules like module-alias you can add more
Then you may run the command like this:
npm run typeorm migration:run -- -d path-to-datasource-config
To reduce verbosity of the documentation, the following sections are using a globally installed typeorm CLI. Depending on how you installed the CLI, you may replace
typeormat the start of the command, by either
npm run typeorm.
You can create a new project with everything already setup:
It creates all files needed for a basic project with TypeORM:
Then you can run
npm installto install all dependencies. After that, you can run your application by running
All files are generated in the current directory. If you want to generate them in a special directory you can use
typeorm init --name my-project
To specify a specific database you use you can use
typeorm init --database mssql
To generate an ESM base project you can use
typeorm init --name my-project --module esm
You can also generate a base project with Express:
typeorm init --name my-project --express
If you are using docker you can generate a
typeorm init --docker
typeorm initis the easiest and fastest way to setup a TypeORM project.
You can create a new entity using CLI:
typeorm entity:create path-to-entity-dir/entity
You can create a new subscriber using CLI:
typeorm subscriber:create path-to-subscriber-dir/subscriber
You can create a new migration using CLI:
typeorm migration:create path-to-migrations-dir/migrationName
Automatic migration generation creates a new migration file and writes all sql queries that must be executed to update the database.
If no there were no changes generated, the command will exit with code 1.
typeorm migration:generate path/to/Migration -d path/to/datasource
The rule of thumb is to generate a migration after each entity change. the -d argument value should specify the path where your DataSource instance is defined. You can specify the path and name of the migration with the first argument.
To execute all pending migrations use following command:
typeorm migration:run -- -d path-to-datasource-config
To revert the most recently executed migration use the following command:
typeorm migration:revert -- -d path-to-datasource-config
This command will undo only the last executed migration. You can execute this command multiple times to revert multiple migrations. Learn more about Migrations.
To show all migrations and whether they've been run or not use following command:
typeorm migration:show -- -d path-to-datasource-config
[X] = Migration has been ran
[ ] = Migration is pending/unapplied
To synchronize a database schema use:
Be careful running this command in production - schema sync may cause data loss if you don't use it wisely. Check which sql queries it will run before running on production.
To check what sql queries
schema:syncis going to run use:
To completely drop a database schema use:
typeorm schema:drop -- -d path-to-datasource-config
Be careful with this command on production since it completely removes data from your database.
You can execute any SQL query you want directly in the database using:
typeorm query "SELECT * FROM USERS"
If you are using
QueryBuildercaching, sometimes you may want to clear everything stored in the cache. You can do it using the following command:
You can check what typeorm version you have installed (both local and global) by running: