tsconfig/bases

Hosts TSConfigs to extend in a TypeScript app, tuned to a particular runtime environment

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 8th, 2026
Created on May 13th, 2020
Open Issues & Pull Requests: 54 (+0)
GitHub issues: Enabled
Number of forks: 286
Total Stargazers: 7,880 (+0)
Total Subscribers: 46 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.6 hours
Mean response time: 33.7 days
90th percentile: 45.3 days
Tracked items: 28

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 9% of issues opened in the past year have been closed. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 612 days
Stale 30+ days: 20
Stale 90+ days: 19

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (1)
  • good first issue (1)
  • you can do this (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

tsconfig/bases is a collection of shareable TypeScript configuration presets tuned for specific runtime environments.

The project solves the problem of TypeScript configuration fragmentation by providing centralized, community-maintained base configurations that developers can extend in their projects. Rather than each project crafting its own tsconfig.json from scratch, developers inherit a vetted baseline appropriate to their target environment—whether Node.js, browser, or other runtimes. This approach mirrors the model of Definitely Typed for type definitions, applying the same community-driven curation to compiler configuration.

Developers should adopt this tool if they want to avoid reinventing TypeScript configuration for common deployment targets. It suits any project that benefits from alignment with established best practices for its runtime, particularly teams that value consistency across multiple codebases. The project targets the latest stable version of TypeScript and coordinates its versioning with the target runtimes it supports, which means version numbers may not follow semantic versioning strictly.

The project maintains active community engagement, with configuration presets regularly reviewed and updated to reflect evolving TypeScript and runtime capabilities. Development follows a deliberate approach to versioning that prioritizes alignment with the ecosystems it targets over strict semver compliance.