tsconfig.json inheritance via Node.js packages

Usage no npm install needed!

<script type="module">
  import chenyuebanTsconfig from 'https://cdn.skypack.dev/@chenyueban/tsconfig';



NPM Version npm (tag)

Clone from tsconfig.

Reusable TypeScript configuration files to extend from.

This module enables other module to inheritance tsconfig.json via Node.js packages


Extends from @chenyueban/tsconfig from your tsconfig.json, to have the chenyueban version of the TypeScript Configuration.


Do not put any directory related configurations into this module. Only put directory related configurations to the consumer of this module.

Because all directory in tsconfig.json is related to the curfrent directory.


TypeScript 3.2 now resolves tsconfig.jsons from node_modules. When using a bare path for the "extends" field in tsconfig.json, TypeScript will dive into node_modules packages for us.

    "extends": "@my-team/tsconfig-base",
    "include": ["./**/*"]
    "compilerOptions": {
        // Override certain options on a project-by-project basis.
        "strictBindCallApply": false,

Here, TypeScript will climb up node_modules folders looking for a @my-team/tsconfig-base package. For each of those packages, TypeScript will first check whether package.json contains a "tsconfig" field, and if it does, TypeScript will try to load a configuration file from that field. If neither exists, TypeScript will try to read from a tsconfig.json at the root. This is similar to the lookup process for .js files in packages that Node uses, and the .d.ts lookup process that TypeScript already uses.

This feature can be extremely useful for bigger organizations, or projects with lots of distributed dependencies.


This module will run a unit test before it could be able to publish to NPM.

The unit test load tsconfig schema from JSON Schema Store and then use is-my-json-valid to validate it.