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

@anacare/tsconfig

v0.1.0

Published

Shared TypeScript configuration presets for the Ana Care platform monorepo. Five presets: base (strict baseline), library (publishable packages), nextjs, expo, nestjs. Published per ADR-0014.

Readme

@anacare/tsconfig — Shared TypeScript presets

Status: in use from day 0. This is the only packages/* that has real content today; everything else is a placeholder until Round 8.

The single source of truth for TypeScript compiler configuration in the monorepo. Every tsconfig.json in apps/* and packages/* (other than @anacare/tsconfig itself) extends one of the presets here.

Presets

| Preset | Use in | Key differences from base | |---|---|---| | base.json | Not used directly — the canonical foundation that every other preset extends. | strict: true + the seven strict-extra flags. Bundler module resolution. ESM-friendly. | | library.json | packages/* (other than this one) | Emits dist/, declarations, source maps. ESNext module. | | nextjs.json | apps/web-admin, apps/client-dashboard | DOM lib. JSX preserve (Next compiles). noEmit: true. Next plugin. | | expo.json | apps/mobile | React Native types. JSX react-jsx. noEmit: true. | | nestjs.json | apps/api | CommonJS module. Node moduleResolution. Decorator metadata enabled. verbatimModuleSyntax: false (decorators need elision). |

How to extend

In a consumer tsconfig.json:

{
  "extends": "@anacare/tsconfig/library",
  "compilerOptions": {
    // Only override what genuinely needs to be different.
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["src"]
}

The extends path uses the package's exports field (package.json). TypeScript 5+ resolves these natively.

Editing rules

  • Changes to base.json ripple to every project. Open an ADR if the change tightens or loosens a strict flag. Loosening a flag is rarely the right answer; usually we add per-app // @ts-expect-error with a comment, or fix the code.
  • Per-app overrides belong in the app's own tsconfig.json, not here.
  • Never remove a flag from base.json without an ADR. The flags catch real bugs in clinical and financial code paths.

Why not just put presets in the repo root?

A package gives us:

  • Versioning via Changesets — a breaking change to base.json is a major bump that consumers explicitly accept.
  • Clean import path (@anacare/tsconfig/library) vs fragile relative paths (../../../tsconfig.base.json).
  • A natural place to add adjacent helpers (e.g., @anacare/tsconfig/types with shared ambient declarations) without sprawling the root.