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

@tsfpp/tsconfig

v1.0.0

Published

Shared TypeScript compiler configuration presets for TSF++ projects

Readme

@tsfpp/tsconfig

Shared TypeScript compiler configuration presets for TSF++ projects.

All mandatory compiler flags from Rule 9.1 are enforced in every preset. Projects extend one of the three presets and add only path, include, and project-specific options on top.

Presets

| Preset | File | Use for | |--------|------|---------| | base | tsconfig.base.json | Foundation for other presets; never extend directly in projects | | lib | tsconfig.lib.json | Publishable npm packages (declaration: true, composite: true) | | app | tsconfig.app.json | Applications and tools (noEmit: true) |

Installation

pnpm add -D @tsfpp/tsconfig typescript

Usage

Library package (tsconfig.json)

{
  "extends": "@tsfpp/tsconfig/lib",
  "compilerOptions": {
    "rootDir": "src"
  },
  "include": ["src"]
}

Application (tsconfig.json)

{
  "extends": "@tsfpp/tsconfig/app",
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "include": ["src", "tests"]
}

Note: The app preset sets "types": ["node"] for ambient type explicitness. Add @types/node as a dev dependency:

pnpm add -D @types/node

Remove or override types if your runtime is not Node.js (e.g. a browser-only app with no Node globals).

Mandatory flags (Rule 9.1)

Every preset enforces the full set of flags required by the TSF++ specification. Flags marked Rule 9.1 are explicitly mandated; the remaining flags are enforced as quality-of-life corollaries that follow directly from the standard's strictness principles.

| Flag | Rule | Why it is mandatory | |------|------|---------------------| | strict | 9.1 | Enables all strict sub-checks | | noUncheckedIndexedAccess | 9.1 | Index access returns T \| undefined, preventing ! violations (Rule 1.6) | | exactOptionalPropertyTypes | 9.1 | Distinguishes absent from undefined (Rule 3.7) | | noImplicitOverride | 9.1 | Requires explicit override keyword | | noFallthroughCasesInSwitch | 9.1 | Enforces exhaustive switch (Rule 4.1) | | useUnknownInCatchVariables | 9.1 | Catch variables are unknown, not any (Rule 1.5) | | verbatimModuleSyntax | 9.1 | Prevents runtime impact from type-only imports | | isolatedModules | 9.1 | Each file must be independently compilable (implied by verbatimModuleSyntax; kept explicit) | | noPropertyAccessFromIndexSignature | 9.1 | Forces bracket notation for dynamic key access | | forceConsistentCasingInFileNames | 9.1 | Prevents cross-platform import casing bugs | | noImplicitReturns | corollary | All code paths must return a value | | noUnusedLocals | corollary | Dead local bindings are a compile error | | noUnusedParameters | corollary | Dead parameters are a compile error; prefix with _ to opt out |

See spec/rationale/09-tooling.md for the extended justification of each flag.

Notes on the lib preset

tsconfig.lib.json emits declarations into dist/types/ and JavaScript into dist/. This separation accommodates toolchains that generate JS via a bundler and use tsc only for type output. If your toolchain expects .d.ts files co-located with .js files, override declarationDir in your local config:

{
  "extends": "@tsfpp/tsconfig/lib",
  "compilerOptions": {
    "rootDir": "src",
    "declarationDir": "dist"
  },
  "include": ["src"]
}

TypeScript version requirement

Requires TypeScript ≥ 5.0. The exports-based extends resolution ("extends": "@tsfpp/tsconfig/lib") was introduced in TypeScript 5.0.