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

@fellwork/tsconfig

v0.2.0

Published

Shared TypeScript configurations for Fellwork projects.

Readme

@fellwork/tsconfig

Shared TypeScript configurations for Fellwork projects.

Four small, composable presets that centralize strictness, security, and best-practice defaults across every Fellwork repo. Built on TS 5.5+ with ${configDir} template-variable support so library emit lands in the consuming package, not in node_modules.

Install

bun add -D -E @fellwork/tsconfig typescript@^5.5

typescript >=5.5.0 is a required peer dependency (for ${configDir} template variable support).

Pick a preset

| Preset | When to use | What it sets | |---|---|---| | base | Generic TS, no environment assumptions | Strict + correctness flags, ES2022 target, ESNext/Bundler resolution, ES2023 lib (no DOM, no Node) | | node | Bun/Node backend code, CLIs | extends base, switches to NodeNext/NodeNext, target ES2023 | | browser | Frontend apps, isomorphic libs | extends base, adds DOM + DOM.Iterable libs | | library | Anything you publish to npm (overlay only) | composite, declaration, declarationMap, sourceMap, ${configDir}/dist outDir |

extends: "@fellwork/tsconfig" (bare, without a subpath) silently resolves to base — prefer @fellwork/tsconfig/base to make the intent explicit.

Quick examples

Backend Node/Bun script

// tsconfig.json
{
  "extends": "@fellwork/tsconfig/node",
  "include": ["scripts/**/*.ts"]
}

Publishable Node library

{
  "extends": [
    "@fellwork/tsconfig/node",
    "@fellwork/tsconfig/library"
  ],
  "include": ["src/**/*.ts"]
}

Publishable browser/isomorphic library

{
  "extends": [
    "@fellwork/tsconfig/browser",
    "@fellwork/tsconfig/library"
  ],
  "include": ["src/**/*.ts"]
}

Nuxt frontend

{
  "extends": [
    "./.nuxt/tsconfig.json",
    "@fellwork/tsconfig/base"
  ]
}

Order matters — Fellwork's strictness comes after Nuxt so it wins.

Composition rules

  1. Pick exactly one environment presetbase, node, or browser.
  2. Add library only if you need to emit .d.ts / declaration maps / participate in project references.
  3. Order matters in array extends: later entries override earlier ones. Always put library last.
  4. Don't extend library alone — it has no target/module/lib. Compose it with an env preset.

Documentation

License

MIT © Shane McGuirt