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

@dral/tsconfig

v1.8.0

Published

My attempt at simple, modern tsconfigs

Readme

@dral/tsconfig

My ready-to-go tsconfigs. Not meant for compilation using tsc, instead for node's typestripping or when building with a bundler. These configs are for universal modules, so no node or DOM types. To provide things like setTimeout and TextEncoder, which are not actually part of ecmascript itself, but are generally available I use "lib": ["WebWorker"], which seems like a nice compromise.

Quick start

Universal package

{
  "extends": [
    "@dral/tsconfig/modern",
    "@dral/tsconfig/universal",
    "@dral/tsconfig/reasonable",
  ],
  "compilerOptions": {},
  "include": ["src"],
}

Node package

{
  "extends": [
    "@dral/tsconfig/modern",
    "@tsconfig/node24",
    "@dral/tsconfig/reasonable",
  ],
  "compilerOptions": {},
  "include": ["src"],
}

Composite (universal package + tests/configs)

Use this template to mix and match different types. If you have other files running like configs, I recommend either adding a separate tsconfig.node.json, or whatever environment the code runs in.

/// tsconfig.json
{
  "files": [],
  "references": [
    { "path": "./tsconfig.universal.json" },
    { "path": "./tsconfig.test.json" },
  ],
}
/// tsconfig.universal.json
{
  "extends": [
    "@dral/tsconfig/modern",
    "@dral/tsconfig/universal",
    "@dral/tsconfig/reasonable",
    "@dral/tsconfig/composite",
  ],
  "compilerOptions": {},
  "include": ["src"],
  "exclude": ["**/*.test.ts"],
}
/// tsconfig.test.json
// {
  "extends": [
    "@dral/tsconfig/modern",
    "@tsconfig/node24",
    "@dral/tsconfig/reasonable",
    "@dral/tsconfig/composite",
  ],
  "compilerOptions": {},
  "include": ["tests", "src/**/*.test.ts"],
  /// Reference to the universal config so we can import the package
  "references": [{ "path": "./tsconfig.universal.json" }],
}

Configs

@dral/tsconfig/modern

Setting up module resolution:

  • Sets noEmit: true because it doesn't work with .ts extensions
  • Forces using exact extensions (.ts, generally)
  • No typescript-only syntax (e.g. enums)

@dral/tsconfig/reasonable

My opinionated config defining what should be errors and what should not. Most of all I don't make unused variables error, because... they aren't errors!

@dral/tsconfig/universal

Currently really just "lib": ["ES2024", "WebWorker"], but I might add some extra "types": [...] for baseline included features (I'm considering browser, Node, Cloudflare Workers, e.g.)

@dral/tsconfig/composite

The odd one out. If you want to use a composite config, things get tricky with emitting and path rewriting, yadi yadi yada. This config makes tsc emit declarations (necessary for references between composite tsconfigs), but sets the build directory to ./node_modules/.cache/@dral/tsconfig/builds, so very much out of the way.