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

@robonen/tsconfig

v0.1.1

Published

Base typescript configuration for projects

Readme

@robonen/tsconfig

Shared TypeScript configurations.

Install

pnpm install -D @robonen/tsconfig

Presets

| Preset | Extends | Use for | | --- | --- | --- | | tsconfig.base.json | — | Node / isomorphic libraries (lib: ESNext, no DOM) | | tsconfig.dom.json | base | Browser libraries (adds DOM, DOM.Iterable) | | tsconfig.vue.json | dom | Vue SFC libraries / apps (adds jsx, vueCompilerOptions) | | tsconfig.node.json | base | Build/test tooling files (*.config.ts) — adds types: ["node"], no DOM | | tsconfig.json | base | Default alias for base (bare @robonen/tsconfig import) |

Usage

Pick the preset that matches the package and extend it:

// Node / isomorphic library
{ "extends": "@robonen/tsconfig/tsconfig.base.json" }
// Browser library
{ "extends": "@robonen/tsconfig/tsconfig.dom.json" }
// Vue package, with path aliases
{
  "extends": "@robonen/tsconfig/tsconfig.vue.json",
  "compilerOptions": {
    "paths": { "@/*": ["./src/*"] }
  }
}

Path aliases resolve relative to the tsconfig.json location — baseUrl is intentionally omitted (deprecated, removed in TypeScript 7.0).

Project references (DOM + Node split)

Most packages contain two environments: browser/library src (DOM) and Node tooling files (vite.config.ts, vitest.config.ts, tsdown.config.ts). They are split into separate projects wired with references, so src never sees Node globals and config files never see DOM:

// tsconfig.json — solution root, tools (tsdown/vitest/editor) target src below
{
  "files": [],
  "references": [
    { "path": "./tsconfig.src.json" },
    { "path": "./tsconfig.node.json" }
  ]
}
// tsconfig.src.json — the library code
{
  "extends": "@robonen/tsconfig/tsconfig.dom.json",
  "compilerOptions": {
    "composite": true,
    "types": [],
    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.src.tsbuildinfo"
  },
  "include": ["src/**/*.ts"]
}
// tsconfig.node.json — build/test tooling files
{
  "extends": "@robonen/tsconfig/tsconfig.node.json",
  "compilerOptions": {
    "composite": true,
    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.node.tsbuildinfo"
  },
  "include": ["*.config.ts"]
}

Type-check the whole package (both projects) with tsc -b / vue-tsc -b. Point tsdown at the src project (tsconfig: './tsconfig.src.json') since the root has no compilerOptions.

What's included (base)

  • Target / Module: ESNext with module: Preserve + Bundler resolution
  • Strict mode: strict, noUncheckedIndexedAccess, noImplicitOverride, noImplicitReturns, noFallthroughCasesInSwitch, noUncheckedSideEffectImports
  • Module safety: verbatimModuleSyntax, isolatedModules, moduleDetection: force
  • Type-check only: noEmit (declarations/output are produced by tsdown)
  • Interop: esModuleInterop, resolveJsonModule