767

I'm having a surprisingly hard time finding an answer to this. With plain Node.JS, you can run any js file with node path/to/file.js, with CoffeeScript it's coffee hello.coffee and ES6 has babel-node hello.js. How do I do the same with Typescript?

My project has a tsconfig.json which is used by Webpack/ts-loader to build a nice little bundle for the browser. I have a need for a build step run from the console before that, though, that would use some of the .ts files used in the project to generate a schema, but I can't seem to be able to run a single Typescript file without compiling the whole project.

21 Answers 21

1012

How do I do the same with Typescript

You can leave tsc running in watch mode using tsc -w -p . and it will generate .js files for you in a live fashion, so you can run node foo.js like normal

TS Node

There is ts-node : https://github.com/TypeStrong/ts-node that will compile the code on the fly and run it through node 🌹

npx ts-node src/foo.ts
13
  • 119
    tsc writes js to disk. ts-node doesn't need to do that and runs ts on the fly
    – basarat
    Commented Jul 2, 2018 at 5:17
  • 9
    just reminder ts-node does not console log from imported modules. For Ex: if you are ts-node fil1.ts and file1.ts uses file2.ts internally, then console logs from file2.ts will not be logged. Commented Oct 11, 2018 at 11:21
  • 25
    ts-node FTW. npm install -g ts-node makes ts-node your-script.ts a breeze. Commented Aug 17, 2019 at 0:50
  • 18
    Since the release of deno, you can now execute deno run path/to/file.ts and it will run typescript files in a single command without compiling it to a separate JS file.
    – JMadelaine
    Commented May 13, 2020 at 23:45
  • 10
    Careful with deno as it is distinct from node and code that will work in node might not work in deno (due to built-in and npm nodejs packages) 🌹
    – basarat
    Commented May 14, 2020 at 0:33
224

Run the below commands and install the required packages globally:

npm install -g ts-node typescript '@types/node'

Now run the following command to execute a typescript file:

ts-node typescript-file.ts
6
  • 5
    this is the best way to do it IMHO, as ts-node also provides TypeScript REPL.
    – tromgy
    Commented Jan 26, 2020 at 19:18
  • 11
    You can also rely on npx ts-node yourscript.ts in case you don't want to use global version. Commented Feb 22, 2020 at 21:41
  • 26
    ts-node doesn't support ES Modules. Commented Mar 5, 2020 at 9:57
  • 3
    The query for the download no longer valid , try npm install typescript --save-dev --global && npm i ts-node -g instead
    – 钟智强
    Commented Nov 5, 2021 at 20:37
  • 1
    ts-node now supports ES Modules, though this support remains experimental because it depends on Node features that are still experimental
    – RichVel
    Commented Nov 11, 2022 at 14:52
124

We have following steps:

  1. First you need to install typescript

    npm install -g typescript
    
  2. Create one file helloworld.ts

    function hello(person){
       return "Hello, " + person;
    }
    let user = "Aamod Tiwari";
    const result = hello(user);
    console.log("Result", result)
    
  3. Open command prompt and type the following command

    tsc helloworld.ts
    
  4. Again run the command

    node helloworld.js
    
  5. Result will display on console

2
  • 27
    In your case ,we run .js file not .ts file. Commented Dec 19, 2018 at 17:07
  • FYI: Be careful this will generate one .js file foreach .ts file
    – mnaa
    Commented Feb 8, 2023 at 10:17
97

You can also try tsx. tsx is a CLI command (alternative to node) for seamlessly running TypeScript, it's built upon esbuild so it's very fast.

https://github.com/esbuild-kit/tsx

Example:

npx tsx ./script.ts
7
  • 1
    Important answer for when speed is critical. Commented Nov 24, 2022 at 21:44
  • 2
    Also important answer when u just want it to work with no hassle, in my case all alternatives had issues Commented Dec 16, 2022 at 21:27
  • 3
    > npx tsx --watch ./script.ts will execute everytime script.ts is modified Commented Dec 16, 2022 at 21:29
  • 1
    How do I debug with chrome web inspector?
    – nvbalaji
    Commented May 21, 2023 at 7:27
  • tsx also works when running it inside a shell script called from an "npm run" script. Don't ask why I had to do that. But ts-node doesn't work in this situation. Commented Feb 5 at 3:58
56

To add to @Aamod answer above, If you want to use one command line to compile and run your code, you can use the following:

Windows:

tsc main.ts | node main.js

Linux / macOS:

tsc main.ts && node main.js
4
  • 7
    npm install typescript -g to install tsc CLI
    – s2t2
    Commented Nov 17, 2019 at 1:59
  • 6
    Ah the windows 'pipe'
    – Rocky Li
    Commented Dec 29, 2019 at 6:28
  • 1
    This wouldn't work if you want to debug typescript source line by line. Commented Jan 20, 2020 at 12:07
  • @s2t2 If you're running typescript in your project there's already a tsc executable in /node_modules/.bin/tsc. This should really be the accepted answer. Commented Sep 18, 2022 at 16:25
53

I created @digitak/esrun, a thin wrapper around esbuild and that executes a TypeScript file almost instantly. esrun was made because I was disappointed with ts-node: too slow, and just didn't work most of the time.

Advantages of esrun over ts-node include:

  • very fast (uses esbuild),
  • can import ESM as well as CJS (just use the libraries of your choice and esrun will work out of the box),
  • there is an included watch mode, run your script with the --watch option and any change to your entry file or any of its dependencies will re-trigger the result
  • you can use esrun in inspect mode to use the DevTools console instead of your terminal console.

After installing, just run:

npx @digitak/esrun file.ts
10
  • 7
    Omg, exactly what I was looking for, for many many hours ! Couldn't make ts-node to work. Simply ran "esrun my-file.ts", and worked out of the box !
    – Random
    Commented Feb 15, 2021 at 13:24
  • 6
    Maybe a little disclaimer that you're the author of the library? Commented Mar 24, 2021 at 19:57
  • 12
    @RobinMétral Yeah, I sometimes find disclaimers ridiculous. I didn't post this for my own publicity but to genuinely help people with the same needs as me. ts-node was troubles and slowness and I wanted to have a modern typescript runner. I also consider it's not really my work since I've only written a small wrapper around the awesome EsBuild library from Evan W - he is the guy who deserves all the credits.
    – Gin Quin
    Commented May 21, 2021 at 9:19
  • 3
    Oh thx for the link @RobinMétral, didn't know it was mandatory. I will update my answer. This library is nothing more than a 77-lines of code wrapper around Esbuild, no need for a 7-collaborators team or an extended test suite for 77 lines of code. All the work is done by Esbuild. People can use it or ts-node or sucrase-node or anything they prefer. I personnally prefer my library because I encountered less issues. Estrella looks awesome but I would not recommand it for this question (nor Esbuild) as they are both build tools and not running tools.
    – Gin Quin
    Commented May 22, 2021 at 19:11
  • 4
    I’m not sure why this wasn’t specified, but to (easily) use this do npx @digitak/esrun index.ts replacing index.ts if required.
    – mxcl
    Commented Aug 26, 2021 at 14:18
49

Edit: May 2022

ts-node now has an --esm flag use it.

Old Answer:

None of the other answers discuss how to run a TypeScript script that uses modules, and especially modern ES Modules.

First off, ts-node doesn't work in that scenario, as of March 2020. So we'll settle for tsc followed by node.

Second, TypeScript still can't output .mjs files. So we'll settle for .js files and "type": "module" in package.json.

Third, you want clean import lines, without specifying the .js extension (which would be confusing in .ts files):

import { Lib } from './Lib';

Well, that's non-trivial. Node requires specifying extensions on imports, unless you use the experimental-specifier-resolution=node flag. In this case, it would enable Node to look for Lib.js or Lib/index.js when you only specify ./Lib on the import line.

Fourth, there's still a snag: if you have a different main filename than index.js in your package, Node won't find it.

Transpiling makes things a lot messier than running vanilla Node.

Here's a sample repo with a modern TypeScript project structure, generating ES Module code.

5
  • 3
    You can use npmjs.com/package/@digitak/esrun which solves the issues mentioned
    – Gin Quin
    Commented Feb 15, 2021 at 11:40
  • Thanks @GinQuin ! esrun did exactly what I expected ts-node to do: SImply run the script with imports.
    – vlz
    Commented Oct 20, 2021 at 17:07
  • Look for my answer ts-node now supports the --esm flag. You answer is my fav! Could you update to help future devs :)
    – bcbrian
    Commented May 4, 2022 at 18:22
  • Reviewer note: @bcbrian - there is no need to edit this information in since you posted an answer yourself. It is perfectly natural for new answers to contain updated information - take the credit. Commented May 5, 2022 at 7:46
  • 2
    Adding --esm doesn't solve the required file extensions on imports issue.
    – Imran
    Commented Sep 29, 2022 at 6:49
20

Just helpful information - here is newest TypeScript / JavaScript runtime Deno.

It was created by the creator of node Ryan Dahl, based on what he would do differently if he could start fresh.

3
  • 5
    Here's an example: deno run https://deno.land/std/examples/welcome.ts
    – mozey
    Commented May 15, 2020 at 12:14
  • 1
    this would be my preferred approach, except for import/require issues with node modules, which is non-trivial to fix
    – hkong
    Commented Feb 4, 2021 at 15:52
  • As tools grow to support Deno's security, I see its ease of use increasing. Including how imports need to have the full relative path/url and file extension. Deno is secure by default. Therefore, unless you specifically enable it, a deno module has no file, network, or environment access for example. add the extra flags while developing. then lock it down: deno run --unstable --allow-read --allow-env main.ts -> dev.to/mxfellner/… Commented May 28, 2021 at 12:43
15

Use bun.

It's faster and has a lot of tooling bundled in.

bun run ./my-script.ts

2
  • 2
    it's really easy!
    – Amoong
    Commented Nov 28, 2023 at 5:56
  • deno too. But you should install either into package.json devDependencies via npm i --save-dev [bun or deno] looking in npmjs for the appropriate packages Commented Jan 8 at 17:17
13

As of May 2022 ts-node does support es modules

npx ts-node --esm file.ts

you will likely need to add "type": "module", to your package.json. And some of the imports might be wonky unless you turn on experimental-specifier-resolution=node

npmjs.com/package/ts-node#commonjs-vs-native-ecmascript-modules

12

For linux / mac you can add the ts-node-script shebang.

Install typescript / ts-node globally (see 1 below for non global install):

npm install ts-node typescript --save-dev --global

Add this as the first line in your .ts file:

#!/usr/bin/env ts-node-script

Then make the file executable:

$ chmod +x ./your-file.ts

You can then run the file directly from the command line:

$ ./your-file.ts

Notes:

1 For non global install you can install local to your project

npm install ts-node typescript --save-dev

and add the relative path to the shebang script eg:

#!/usr/bin/env ./node_modules/.bin/ts-node-script

2 Support for shebangs was officially added in ts-node v8.9.0.

9

Write yourself a simple bash wrapper may helps.

#!/bin/bash
npx tsc $1 && node ${1%%.ts}
7

Like Zeeshan Ahmad's answer, I also think ts-node is the way to go. I would also add a shebang and make it executable, so you can just run it directly.

  1. Install typescript and ts-node globally:

    npm install -g ts-node typescript
    

    or

    yarn global add ts-node typescript
    
  2. Create a file hello with this content:

    #!/usr/bin/env ts-node-script
    
    import * as os from 'os'
    
    function hello(name: string) {
        return 'Hello, ' + name
    }
    const user = os.userInfo().username
    console.log(`Result: ${hello(user)}`)
    

    As you can see, line one has the shebang for ts-node

  3. Run directly by just executing the file

    $ ./hello
    Result: Hello, root
    

Some notes:


Update 2020-04-06: Some changes after great input in the comments: Update shebang to use ts-node-script instead of ts-node, link to issues in ts-node.

2
  • 4
    ts-node doesn't support ES Modules. Commented Mar 5, 2020 at 9:58
  • 1
    You can run into many problems with this approach. I documented potential solutions in this issue. In particular, the shebang #!/usr/bin/env ts-node-script (also part of ts-node) seems to be superior for this purpose. If you want to link your script (e.g. with npm link), things get more complicated as the script mode of ts-node does not (yet?) follow symbolic links. I went with #!/usr/bin/env -S ts-node --project /usr/local/lib/node_modules/<your-project>/tsconfig.json in the end in my case. Commented Apr 3, 2020 at 23:11
7

For environments such as Webstorm where the node command cannot be changed to ts-node or npx:

  1. npm install ts-node typescript (Install dependencies)
  2. node --require ts-node/register src/foo.ts (Add --require ts-node/register to "Node parameters")
1
  • You can change the Node interpreter in WebStorm. In the Run/Debug configuration, you can select any binary you want as the Node interpreter. Commented Feb 15, 2021 at 13:18
7

Here is the command

tsc index.ts --outDir .temp && node .temp/index.js && rm -rf .temp
<<<<<<<<< Compile >>>>>>>>> <<<<<<< Run >>>>>>> << Clean >>

4
  1. Create your TypeScript file (ex. app.ts)
  2. npm i -D typescript ts-node -> to install the dev dependencies local
  3. npx nodemon app.ts

Using nodemon, automatically recompile app.ts every time you change the file

3

Just in case anyone is insane like me and wants to just run typescript script as though it was a .js script, you can try this. I've written a hacky script that appears to execute the .ts script using node.

#!/usr/bin/env bash

NODEPATH="$HOME/.nvm/versions/node/v8.11.3/bin" # set path to your node/tsc

export TSC="$NODEPATH/tsc"
export NODE="$NODEPATH/node"

TSCFILE=$1 # only parameter is the name of the ts file you created.

function show_usage() {
    echo "ts2node [ts file]"
    exit 0
}

if [ "$TSCFILE" == "" ]
then
    show_usage;
fi

JSFILE="$(echo $TSCFILE|cut -d"." -f 1).js"

$TSC $TSCFILE && $NODE $JSFILE

You can do this or write your own but essentially, it creates the .js file and then uses node to run it like so:

# tsrun myscript.ts

Simple. Just make sure your script only has one "." else you'll need to change your JSFILE in a different way than what I've shown.

1
  1. Install ts-node node module globally.
  2. Create node runtime configuration (for IDE) or use node in command line to run below file js file (The path is for windows, but you can do it for linux as well) ~\AppData\Roaming\npm\node_modules\ts-node\dist\bin.js
  3. Give your ts file path as a command line argument.
  4. Run Or Debug as you like.
1
  • This is the way you need to do it if you want to debug with an IDE! Thanks for this!!
    – nerdlinger
    Commented Jan 3, 2021 at 22:25
0

There is also an option to run code directly from the CLI, not the *.ts file itself.

It's perfectly described in the ts-node manual.

  1. As a first step, install ts-node globally via npm, yarn, or whatever you like.
  2. ...and now just use ts-node -e 'console.log("Hello, world!")' (you may also add the -p flag for printing code)

This little command is perfect for checking, does everything installed fine. And for finding some other error, relevant with tsconfig.json options.

0

I tried the following as a workaround to run ts files from command line

tsc --watch // compile, generate js files and watch for any later changes
node index.js // you can replace node with nodemon as well to automatically restart your app
-3

We can run it using nodemon as well

nodemon ./filepath/filename.ts

Not the answer you're looking for? Browse other questions tagged or ask your own question.