@qntx/tsconfig

Shared TSConfig configs for QuantX projects. One package, many configs.

Forked and reworked from tsconfig/bases.

Install

npm install --save-dev @qntx/tsconfig
# or
bun add -d @qntx/tsconfig

Usage

{
  "extends": "@qntx/tsconfig/configs/node-lts.json"
}

Combine multiple configs (TypeScript 5.0+):

{
  "extends": ["@qntx/tsconfig/configs/strictest.json", "@qntx/tsconfig/configs/node24.json"]
}

Inspect the resolved config:

tsc --showConfig

Available configs

All files under configs/. Common ones:

| Config | Path | | ----------- | ----------------------------------------- | | Recommended | @qntx/tsconfig/configs/recommended.json | | Strictest | @qntx/tsconfig/configs/strictest.json | | Node LTS | @qntx/tsconfig/configs/node-lts.json | | Node 24 | @qntx/tsconfig/configs/node24.json | | Bun | @qntx/tsconfig/configs/bun.json | | Next.js | @qntx/tsconfig/configs/next.json | | Vite React | @qntx/tsconfig/configs/vite-react.json |

node-ts is meant to be combined with a Node config (TypeScript 5.8+):

{
  "extends": ["@qntx/tsconfig/configs/node22.json", "@qntx/tsconfig/configs/node-ts.json"]
}

Development

Requires Bun.

bun install   # also installs husky commit-msg hook
bun run check
bun run fmt        # format with oxfmt (JSON/JSONC/…)
bun run fmt:check  # CI-friendly check

Commits follow Conventional Commits (enforced by commitlint + husky).

Publish:

1. Bump version in package.json (e.g. 1.0.1)
2. Commit and push
3. Create and push a matching tag:

git tag v1.0.1
git push origin v1.0.1

Pushing v* tags runs Publish @qntx/tsconfig automatically (OIDC Trusted Publishing, no npm token).

Local first publish (already done for 1.0.0) or emergency:

npm publish --access public

Layout

configs/   # published package files
example/   # local smoke example (relative extends)