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

@langri-sha/tsconfig

v3.0.0

Published

A set of TypeScript configuration files, focused on type-checking all your TypeScript and JavaScript modules

Readme

@langri-sha/tsconfig

Shared TypeScript configurations that type-check TypeScript and JavaScript alike, with variants for monorepos, React and Emotion.

Usage

Install the necessary dependencies:

npm install -D typescript @langri-sha/tsconfig

Then extend the base configuration:

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "@langri-sha/tsconfig"
}

To combine configurations, list them in this order — later entries win:

  1. A base: @langri-sha/tsconfig, @langri-sha/tsconfig/project.json for a package inside a monorepo, or @langri-sha/tsconfig/build.json for a library that emits, React or Emotion ones included.
  2. @langri-sha/tsconfig/react.json for React.
  3. @langri-sha/tsconfig/emotion.json for Emotion, which also needs react.json.

For example, an Emotion app inside a monorepo:

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": [
    "@langri-sha/tsconfig/project.json",
    "@langri-sha/tsconfig/react.json",
    "@langri-sha/tsconfig/emotion.json"
  ]
}

The monorepo's root tsconfig.json extends the base and lists each package as a project reference:

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "@langri-sha/tsconfig",
  "references": [{ "path": "./packages/app" }]
}

Strictness and module options

TypeScript 6 or 7 is required. On top of their defaults, which include strict, the base sets, among others:

  • verbatimModuleSyntax: import types with a type modifier. An import whose every named binding is an inline type, as in import { type Name } from 'module', still leaves import {} from 'module' in the output; import type { Name } from 'module' drops it.
  • erasableSyntaxOnly: no enums, namespaces with values, parameter properties or angle-bracket type assertions. Set it to false in a package that needs them.
  • noImplicitReturns and moduleDetection: "force".
  • lib: ["ES2025"], which doesn't declare APIs Node 24 lacks, such as Temporal.

Emitting

The base only type-checks. It doesn't set rootDir, which TypeScript 6 no longer infers, so a project that emits through it fails with TS5011 when its sources sit in a subdirectory such as src. A project that emits JavaScript or declarations extends @langri-sha/tsconfig/build.json instead, which sets rootDir to src:

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "@langri-sha/tsconfig/build.json",
  "include": ["src"]
}

See

Contributing

See CONTRIBUTING.md in langri-sha/github.