What TypeScript configuration produces output closest to Node.js 14 capabilities?

Issue

With Node.js bringing updated support for ES2020 and adding support for ES modules, how can TypeScript be configured to output JavaScript code that takes advantage of all these new features?

Solution

As of Node.js 14.0.0, 100% of ES2020 is supported, and support for ES Modules has landed! If you know that you are targeting that version or newer, the optimal config would look like this:

  • "module": "ES2020" & "moduleResolution": "node"

    Node.js 14 support loading modules instead of the old CommonJS format, we do thave to tell TypeScript that we are using Node.js’s rules for resolving modules.

  • "allowSyntheticDefaultImports": true

    To provide backwards compatibility, Node.js allows you to import CommonJS packages with a default import. This flag tells TypeScript that it’s okay to use import on CommonJS modules.

  • "target": "ES2020"

    This tells TypeScript that it’s okay to output JavaScript syntax with features from ES2020. In practice, this means that it will e.g. output optional chaining operators & async/await syntax instead of embedding a polyfill.

  • "lib": ["ES2020"]

    This tells TypeScript that it’s okay to use functions and properties introduced in ES2020 or earlier. In practice, this means that you can use e.g. Promise.allSettled and BigInt.

The full config would thus be:

{
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "lib": ["ES2020"],
    "module": "ES2020",
    "moduleResolution": "node",
    "target": "ES2020"
  }
}

In addition to this, we also need to tell Node.js to treat .js files in this project as ES Modules. The reason for this is that Node.js had to maintain backwards compatibility with code written for older Node.js versions. This can be done by adding "type": "module" to your package.json:

{
  "type": "module"
}

Another change if you are comming from an earlier version of Node.js is that the file extension when importing files are now mandatory. This means that you must write out .js at the end of your local imports. Note that this is .js even though you are importing a TypeScript file that actually has the file extension .ts. This might seem a bit confisuing but this comment from one of the TS contributors explains why that is.

Here are some examples of how to write your import statements:

// Built-in Node.js modules
import { readFileSync } from 'fs'

// CommonJS packages from Npm
import md5File from 'md5-file'

// The local file "a.ts"
import { a } from './a.js'

If you want to stick with CommonJS for now, to avoid the caveats explained above, you can use the following config:

{
  "compilerOptions": {
    "lib": ["ES2020"],
    "module": "CommonJS",
    "target": "ES2020"
  }
}

If you are running Node.js 18 you can see my similar answer for Node.js 18 here

If you are running Node.js 16 you can see my similar answer for Node.js 16 here

If you are running Node.js 12 you can see my similar answer for Node.js 12 here

If you are running Node.js 10 you can see my similar answer for Node.js 10 here

If you are running Node.js 8 you can see my similar answer for Node.js 8 here

Answered By – Linus Unnebäck

Answer Checked By – Mildred Charles (AngularFixing Admin)

Leave a Reply

Your email address will not be published.