npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@draft0/tsconfig

v0.1.0

Published

Opinionated tsconfig presets to help you ship faster.

Readme

@draft0/tsconfig

Skip setup, start shipping.

⚠️ This package is in beta preview and its API is subject to change.

@draft0/tsconfig is part of Draft0, an opinionated, zero-configuration toolkit for modern TypeScript projects.

This package provides ready-to-use TypeScript tsconfig presets so you can use strict, modern defaults immediately and focus on your code.

Use it as an extends layer in your project tsconfig.json, then add your own include, exclude, aliases, and output-specific overrides.

Install

npm install -D @draft0/tsconfig typescript

Usage

// tsconfig.json
{
  "extends": "@draft0/tsconfig/tsc/dom/app",
  "compilerOptions": {
    "jsx": "react-jsx",
  },
  "include": ["src/**/*.ts", "src/**/*.tsx"],
  "exclude": ["node_modules"],
}

Pick a preset in 30 seconds

1) Choose runtime path

  • TypeScript compiles your final JavaScript → use tsc/...
  • A bundler or framework handles build output → use bundler/...

2) Choose environment

  • DOM available (browser apps) → .../dom/...
  • No DOM (Node, CLI, server runtime) → .../no-dom/...

3) Choose output type

  • Application code.../.../app
  • Library code.../.../lib

Examples

  • Browser app using tsc: @draft0/tsconfig/tsc/dom/app
  • Node service using tsc: @draft0/tsconfig/tsc/no-dom/app
  • Browser app with bundler: @draft0/tsconfig/bundler/dom/app

Framework presets

If you use one of these frameworks, start from its dedicated preset and only add project-specific fields:

| Framework | Preset | | --------------------------------------------------------- | -------------------------------------------- | | Analog | @draft0/tsconfig/frameworks/analog | | Angular | @draft0/tsconfig/frameworks/angular | | Astro | @draft0/tsconfig/frameworks/astro | | Ember | @draft0/tsconfig/frameworks/ember | | Lit | @draft0/tsconfig/frameworks/lit | | NestJS | @draft0/tsconfig/frameworks/nestjs | | Next.js | @draft0/tsconfig/frameworks/nextjs | | Nuxt | @draft0/tsconfig/frameworks/nuxt | | Preact | @draft0/tsconfig/frameworks/preact | | Qwik | @draft0/tsconfig/frameworks/qwik | | React Native | @draft0/tsconfig/frameworks/react-native | | React Router (framework mode) | @draft0/tsconfig/frameworks/react-router | | Remix | @draft0/tsconfig/frameworks/remix | | Solid | @draft0/tsconfig/frameworks/solid | | Svelte | @draft0/tsconfig/frameworks/svelte | | SvelteKit | @draft0/tsconfig/frameworks/svelte-kit | | TanStack Start | @draft0/tsconfig/frameworks/tanstack-start | | Vue | @draft0/tsconfig/frameworks/vue |

Some frameworks also generate their own tsconfig (for example Nuxt and SvelteKit). In those cases, follow the framework’s docs for merge order so generated path aliases stay intact.

Examples

Add include and exclude yourself to fit your repo layout.

Next.js app

{
  "extends": "@draft0/tsconfig/frameworks/nextjs",
  "compilerOptions": {
    "paths": {
      "@/*": ["./*"],
    },
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", "**/*.mts", ".next/types/**/*.ts"],
  "exclude": ["node_modules"],
}

NestJS API (src-based project)

{
  "extends": "@draft0/tsconfig/frameworks/nestjs",
  "compilerOptions": {
    "rootDir": "./src",
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist"],
}

Vite-style frontend (no framework preset)

{
  "extends": "@draft0/tsconfig/bundler/dom/app",
  "include": ["src/**/*.ts", "src/**/*.tsx", "src/**/*.vue"],
  "exclude": ["node_modules", "dist"],
}

Draft0 Core only

All presets inherit from a strict Draft0 Core config (ES2025 target, strict mode, stronger module/type-checking defaults). If you only want those defaults, use:

{
  "extends": "@draft0/tsconfig/core",
}

Documentation

Full documentation: draft0.dev.