Using CLI
Last updated
Was this helpful?
Last updated
Was this helpful?
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.
This CLI tool is written in javascript and to be run on node. If your entity files are in typescript, you will need to transpile them to javascript before using CLI. You may skip this section if you only use javascript.
You may setup ts-node in your project to ease the operation as follows:
Install ts-node:
Add typeorm command under scripts section in package.json
For ESM projects add this instead:
Then you may run the command like this:
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 typeorm
at the start of the command, by either npx typeorm
or npm run typeorm
.
You can create a new project with everything already setup:
It creates all files needed for a basic project with TypeORM:
.gitignore
package.json
README.md
tsconfig.json
src/entity/User.ts
src/index.ts
Then you can run npm install
to install all dependencies. After that, you can run your application by running npm start
.
All files are generated in the current directory. If you want to generate them in a special directory you can use --name
:
To specify a specific database you use you can use --database
:
To generate an ESM base project you can use --module esm
:
You can also generate a base project with Express:
If you are using docker you can generate a docker-compose.yml
file using:
typeorm init
is the easiest and fastest way to setup a TypeORM project.
You can create a new entity using CLI:
You can create a new subscriber using CLI:
You can create a new migration using CLI:
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.
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:
To revert the most recently executed migration use the following command:
To show all migrations and whether they've been run or not use following command:
[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:sync
is going to run use:
To completely drop a database schema use:
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:
If you are using QueryBuilder
caching, 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:
If you want to load more modules like you can add more --require my-module-supporting-register
Learn more about .
Learn more about .
Learn more about .
Learn more about .
Learn more about .
This command will undo only the last executed migration. You can execute this command multiple times to revert multiple migrations. Learn more about .