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

@envsa/typescript-config

v9.0.13

Published

TypeScript configuration for @envsa/shared-config.

Readme

@envsa/typescript-config

NPM Package @envsa/typescript-config License: MIT

TypeScript configuration for @envsa/shared-config.

Overview

It's a shared TypeScript tsconfig.json config, plus a command-line tool envsa-typescript to perform TypesScript-related validation and linting.

[!IMPORTANT]

You can use this package on its own, but it's recommended to use @envsa/shared-config instead for a single-dependency and single-package approach to linting and fixing your project.

This package is included as a dependency in @envsa/shared-config, which also automatically invokes the command line functionality in this package via its envsa command

Setup

[!NOTE]

The package treats typescript as a peer dependency - it expects you to have typescript installed in your project.

To use just this TypeScript config in isolation:

  1. Install the .npmrc in your project root. This is required for correct PNPM behavior:
pnpm dlx @envsa/repo-config init
  1. Add the package:
pnpm add -D @envsa/typescript-config
  1. Add the starter tsconfig.json and tsconfig.build.json files to your project root, and add any customizations you'd like:
pnpm exec envsa-typescript init

Usage

You can call envsa-typescript directly, or use the script bundled with the config. Integrate wih your package.json script as you see fit, for example:

{
  "scripts": {
    "lint": "envsa-typescript lint"
  }
}

Ignoring files

See the tsconfig.json exclude key. .gitignore files are not ignored.

Ignoring code

See the TypeScript directive comments documentation for more details.

Entire files (at top):

/* @ts-nocheck */

Next line:

/* @ts-ignore */

or

/* @ts-expect-error - reason */

CLI

Command: envsa-typescript

Envsa's TypeScript shared configuration tools.

This section lists top-level commands for envsa-typescript.

Usage:

envsa-typescript <command>

| Command | Description | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | init | Initialize by copying starter config files to your project root. | | lint | Run type checking on your project. Package-scoped. In a monorepo, it will also run in all packages below the current working directory. | | print-config | Print the TypeScript configuration for the project. Package-scoped. Searches up to the root of a monorepo if necessary. |

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

See the sections below for more information on each subcommand.

Subcommand: envsa-typescript init

Initialize by copying starter config files to your project root.

Usage:

envsa-typescript init

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

Subcommand: envsa-typescript lint

Run type checking on your project. Package-scoped. In a monorepo, it will also run in all packages below the current working directory.

Usage:

envsa-typescript lint

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

Subcommand: envsa-typescript print-config

Print the TypeScript configuration for the project. Package-scoped. Searches up to the root of a monorepo if necessary.

Usage:

envsa-typescript print-config

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

Notes

General

Other shared tsconfig projects

Future integrations

Credits

Eric Mika is the author of the original @kitschpatrol/shared-config project on which this is based.

License

MIT © Liam Rella