I’m using Typescript daily with angular since 6 months and see the positive impact on my workflow and the code I produce. So I decided to use it on the Node side too, but it wasn’t an easy task to have the setup I wanted!

I didn’t find a place with all explanations up to date and using latest tools so I post it there to hopefully help some of you. ;)

Scroll down to find full JSON files details.

A. Produce code compatible with Node:

NodeJS needs compatible JS files in input to work, so configure your tsconfig.json with these properties:

  • "target": "es6" Or "es5" if you are using a Node version older than 6.
  • "module": "commonjs" It tells compiler to convert all ES6 modules (import/export) to CommonJS modules (require/module.exports).

B. Always lunch the app with transpiled JS files from latest TS files:

➜ VSCode automatically displays your TS error.

You don’t need to run the Typescript compiler in watch mode. Inside tsconfig.json, add property "watch": false.

➜ Configure VSCode debugging.

Use lunch.json config file for debugging session start and tasks.json to create a task which run Typescript compiler.

  • Inside lunch.json, add property "preLaunchTask": "tsc" to force Typescript compilation before app start.
  • Inside tasks.json, add properties "command": "tsc" and "isShellCommand": true to make a task named tsc running Typescript compiler.
  • Inside tsconfig.json, add property "noEmitOnError": true to make compiler throw error when something wrong.

Now when starting your app with F5 (Or Debug panel > Start Debugging), if your TS files are not valid you will see the following message letting you stop debugging to correct it before lunch it again:

Build error has been detected during preLaunchTask 'tsc'. DEBUG ANYWAY / CLOSE

C. Debug with breakpoints inside TS files:

➜ Add MAP files support.

  • Inside tsconfig.json, add property "sourceMap": true.
  • Inside lunch.json, add property "sourceMaps": true.

➜ Help VSCode find JS/MAP files linked to your TS files.

Having TS files and JS/MAP files in separate folders is a good practise. To implement it:

  • Inside tsconfig.json, add property "outDir": "dist".
  • Inside lunch.json, add property "outDir": "${workspaceRoot}/dist"

D. Use @typings/* to add external module definitions files:

  • Run this command to install node definition file and lodash and express definition files: npm i --save-dev "@typings/node" "@typings/lodash" "@typings/express"

It installs definitions files like any others node modules and Typescript compiler automatically check /node_modules/@typings/lodash when looking for definitions.

Some node modules now include definitions files directly bundled with it (angular2 do it). More details about it.

Keep in mind that your library vs library definition versions could be different, it can leads you to “weird” cases like:

  • Typescript say something is good but at execution it throws an error because wrong definition file!
  • Typescript tells you this function doesn’t exist in this module or with differents parameters but in really it does!

To avoid this, compare these 2 versions and don’t hesitate to go throught your installed definition files.

For example, you can see all availables versions here:

E. Know when use ES6 or CommonJS module syntax:

➜ ES6 module syntax (import/export)

  • Use it between all your project TS files.
  • Use it to import external modules having definitions files (node/express/lodash,.. in my case).

➜ CommonJS module syntax (require/module.exports)

  • Use it only to import external modules without definitions files. Typescript is ok with it because require definition is inside the node definition file we import from @typings/node.

It’s weird to mix ES6 and CommonJS module syntax at first but keep in mind it will be always CommonJS modules inside your transpiled JS files.

F. Make your custom types/interfaces definitions available everywhere:

In my humble opinion, import interfaces definitions in your TS files while they are here just to development workflow and disappear when transpiled to JS files is a bad practise.

So, to make it accessible from everywhere inside your project (and never import/export them), declare all your interfaces inside definitions files *.d.ts.

Config files sources:

➜ File “/package.json”:

  "name": "demo-project",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "node ./bin/www"
  "dependencies": {
    "bluebird": "^3.4.6",
    "body-parser": "~1.15.2",
    "cookie-parser": "~1.4.3",
    "debug": "~2.2.0",
    "express": "~4.14.0",
    "lodash": "^4.17.2",
    "mysql": "^2.12.0",
  "devDependencies": {
    "@types/express": "^4.0.34",
    "@types/lodash": "^4.14.40",
    "@types/node": "^6.0.49"

➜ File “/tsconfig.config”:

  "compilerOptions": {
    "target": "es6",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "strictNullChecks": true,
    "skipLibCheck": true,
    "noImplicitAny": false,
    "noEmitOnError": true,
    "watch": false,
    "outDir": "dist"
  "exclude": [

➜ File “/.vscode/tasks.json”:

    "version": "0.1.0",
    "command": "tsc",
    "isShellCommand": true,
    "showOutput": "always"

➜ File “/.vscode/lunch.json”:

    "version": "0.2.0",
    "configurations": [
            "type": "node",
            "request": "launch",
            "name": "Launch program",
            "program": "${workspaceRoot}\\bin\\www",
            "cwd": "${workspaceRoot}",
            "outFiles": [],
            "sourceMaps": true,
            "outDir": "${workspaceRoot}/dist",
            "preLaunchTask": "tsc",
            "env": {
                "NODE_ENV": "development"