Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2026 – Pkg Stats / Ryan Hefner

@howells/typescript-config

v0.1.0

Published

a day ago

Pinned wrappers and overlays around @total-typescript/tsconfig.

0High
0Medium
0Low

`@howells/typescript-config`

Pinned wrappers and thin overlays around @total-typescript/tsconfig.

The goal is not to invent a second tsconfig philosophy. The goal is to:

pin a specific upstream @total-typescript/tsconfig version
give every consumer the same decision matrix
keep only a few house overlays for framework and runtime cases

Install

npm install -D @howells/typescript-config

Core Presets

These map directly to the Total TypeScript decision tree:

@howells/typescript-config/bundler-dom-app
@howells/typescript-config/bundler-dom-library
@howells/typescript-config/bundler-dom-library-monorepo
@howells/typescript-config/bundler-no-dom-app
@howells/typescript-config/bundler-no-dom-library
@howells/typescript-config/bundler-no-dom-library-monorepo
@howells/typescript-config/tsc-dom-app
@howells/typescript-config/tsc-dom-library
@howells/typescript-config/tsc-dom-library-monorepo
@howells/typescript-config/tsc-no-dom-app
@howells/typescript-config/tsc-no-dom-library
@howells/typescript-config/tsc-no-dom-library-monorepo

Overlays

These are intentionally small:

@howells/typescript-config/nextjs
@howells/typescript-config/react-library

Examples

Next.js app:

{
  "extends": "@howells/typescript-config/nextjs"
}

React package in a monorepo:

{
  "extends": "@howells/typescript-config/react-library"
}

Non-DOM app checked by TypeScript but built elsewhere:

{
  "extends": "@howells/typescript-config/bundler-no-dom-app"
}

Library emitted by tsc:

{
  "extends": "@howells/typescript-config/tsc-no-dom-library"
}

Rules

Do not put consumer-local paths or baseUrl in these shared presets.
Do not put workspace-specific types in shared presets unless the preset is explicitly runtime-specific.
Do not reintroduce a universal base.json that hides runtime and emit decisions.
Treat changes in compiler behavior as breaking changes when versioning this package.

Upstream

This package follows Matt Pocock's guidance and wraps:

https://www.totaltypescript.com/tsconfig-cheat-sheet
https://github.com/total-typescript/tsconfig