@voxpelli/tsconfig v12.0.1

@voxpelli/tsconfig

My personal types in js focused tsconfig bases.

Are meant to be used with javascript code, not typescript code, hence they're having eg. noEmit: true set.

Usage

npm install --save-dev @voxpelli/tsconfig

Then in your tsconfig.json, it extends the chosen base config:

{
  "extends": "@voxpelli/tsconfig/node20.json",
  "files": [
    "index.js"
  ],
  "include": [
    "test/**/*",
  ]
}

Available configs

Generic ones

• base – where most of the configuration is set
• legacy – like base but for older TypeScript versions – version 4.5 and onward
• recommended – like base but adds a target set to ES2015

Node specific ones

These extends base with the correct lib and target for the node.js version.

Inspired by tsconfig/bases.

• node20
• node18
• node16
• node14

Can I use this in my own project?

Absolutely, my pleasure!

Just as with voxpelli/eslint-config I follow Semantic Versioning and thus won't do any breaking changes in any non-major releases.

Give me a ping if you use it, would be a delight to know you like it 🙂

Alternatives

• sindresorhus/tsconfig
• tsconfig/bases

My other reusable configs

• voxpelli/eslint-config – the reusable ESLint setup I use in my projects
• voxpelli/ghatemplates – the reusable GitHub Actions workflows I use in my projects
• voxpelli/renovate-config-voxpelli – the reusable Renovate setup I use in my projects