OSS Tanbou
Sign in with GitHub

@sindresorhus/tsconfig

View on GitHub

A shared package for applying strict TypeScript settings across Node.js projects

OSS scale score 136.6OSS health 42Update pace 0 commits/30d
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
377
License
MIT
Repository last updated
Oct 31, 2025
On this page

Overview

@sindresorhus/tsconfig packages a reusable TypeScript compiler configuration. Projects extend it from tsconfig.json to keep type-checking rules consistent without copying the full option set.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Inherit a common compiler configuration

Install the package as a development dependency and extend “@sindresorhus/tsconfig” from tsconfig.json. It bundles checks such as strict, noUncheckedIndexedAccess, and noImplicitOverride together with declaration output settings.

Sources: [1][2]

Best fit

Standardize checks for Node.js libraries

It fits teams maintaining several TypeScript packages or starting a library with a concise configuration. Running npx tsc --noEmit in a small sample shows the compiler result under the inherited rules.

Sources: [1][2]

Before adoption

Check runtime targets and migration impact

Version 8.1.0 requires TypeScript 5.9 or later and Node.js 20 or later. Its target is esnext and the config performs no polyfilling, so code must use only syntax and APIs supported by the deployment environment.

Sources: [1][3]

Official sources

  1. [1]tsconfig v8.1.0 README(2026-10-04)
  2. [2]tsconfig v8.1.0 compiler options(2026-10-04)
  3. [3]tsconfig v8.1.0 release(2026-10-04)
Supplemental curator note

These strict settings reflect the maintainer’s own projects. Test them on a small scope first because existing code may surface unused declarations, unsafe indexed access, and other new errors.

Try it in 3 steps

  1. 1

    Create a sample project

    Confirm that Node.js 20 or later is active, then create an empty Node.js project and enter its directory for the remaining steps.

    mkdir tsconfig-demo && cd tsconfig-demo && npm init -y
  2. 2

    Install pinned config and compiler versions

    Install the reviewed config release and a TypeScript version that satisfies its requirement.

    npm install --save-dev typescript@5.9.3 @sindresorhus/tsconfig@8.1.0
  3. 3

    Extend the config and type-check

    Write a minimal config and source file, then confirm the inherited compiler rules accept the sample.

    printf '%s\n' '{"extends":"@sindresorhus/tsconfig","compilerOptions":{"noEmit":true}}' > tsconfig.json && printf '%s\n' 'export const greeting: string = "hello";' > index.ts && npx tsc --noEmit
Check the official README

Growth

Growth trends · Last 30 days

377 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
0
Open PRs
0

Development activity is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • tsconfig
  • typescript
  • config
  • npm-package
Stars
377
Forks
32
Watchers
14
Open issues
4
Contributors
8
Owner type
User
License
MIT
Repository last updated
Oct 31, 2025
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?