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

@mitcsutt/kiln-tsconfig

v0.2.0

Published

Shared TypeScript presets for Kiln and the projects that use it

Readme

@mitcsutt/kiln-tsconfig

Shared TypeScript presets for Kiln and the projects that use it.

Install

pnpm add -D @mitcsutt/kiln-tsconfig typescript

Usage

Extend one preset, or combine several. Later presets win, and every preset carries base's lib, so put react last to keep the DOM libraries:

{
  "extends": ["@mitcsutt/kiln-tsconfig/library", "@mitcsutt/kiln-tsconfig/react"],
  "include": ["src"]
}

| Preset | What it sets | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | base | strict, noUncheckedIndexedAccess, noImplicitOverride, verbatimModuleSyntax, isolatedModules, Bundler resolution, ES2022 target | | react | base, plus the DOM libraries and the automatic JSX runtime | | library | base, plus declarations, declaration maps and source maps | | app | base, plus noEmit and allowJs, for apps that a bundler or framework builds | | react-app | react and app in one preset, for React apps | | node | base, with Node.js module resolution (NodeNext) and Node.js types, for scripts and tooling. It needs @types/node. |

For a React app, extend react-app rather than ["app", "react"]. Both of those extend base, and esbuild (which Vite and Vitest run) prints Base config file "./base.json" forms cycle for a config that reaches base twice. react-app reaches it once.

Every preset can also be imported with its .json extension, for example @mitcsutt/kiln-tsconfig/base.json.

Docs

Full documentation lives on the Kiln docs site.

Licence

MIT