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

@its-tailtime/tsconfig

v1.0.3

Published

A Typescript shareable config

Readme

tsconfig

A Typescript shareable config.

Typescript dependency

Note that the version range specified for the typescript package peer dependency is using a >= specifier rather than the usual ^ specifier.

Why? ^ would be the correct specifier to use for a dependent package that uses semver, so that the consuming package gets minor & patch version updates - but never a breaking change that comes from a major version change.

But the typescript package doesn't follow semver :( Instead they say that no breaking changes are ever expected.. which we'll see about (sources: https://github.com/microsoft/TypeScript/issues/39269, https://www.semver-ts.org/, and so on).

For this reason - ensure that you are pinning to a specific version of typescript in your package-lock.json file.

Installation

Run the following command (this will also install dependencies):

pnpm add --save-dev @its-tailtime/tsconfig

Then, create a tsconfig.json file at the root of your repository containing the following:

{
  "extends": "@its-tailtime/tsconfig",
  "compilerOptions": {
    "types": [] // Add your global types here - e.g. ['node'] for node apps, ["webpack-env", "jest"] for legacy vue apps
  },
  "include": ["src/**/*.vue", "src/**/*.ts", "tests/**/*.ts", "*.ts"],
  "exclude": ["node_modules"]
}

Filepaths such as include & exclude must be specified per repository as they're not shareable.

You can override settings from the shareable config by adding them directly into your tsconfig.json file.

Exports

tsconfig.json

Default Typescript configuration export which should be used for common purposes.

node.json

For packages intended to be consumed by node-oriented apps / libraries. We just use tsup to build node libraries, rather than Vite (which isn't really designed for building Node.js-based code as it's more browser-oriented) or Typescript itself (as it's dog slow). Additional settings are required on top of the base ones to support building a node-oriented library.

  • We set "importHelpers": false to resolve https://github.com/microsoft/TypeScript/issues/37991 for node packages built in Typescript.

scripts.json

Typescript configuration for internal scripts.