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

tsc-mono

v2.1.2

Published

Super simple typescript mono-repo tooling.

Downloads

45

Readme

tsc-mono

Super simple typescript mono-repo tooling.

It is recommended that you use at least TypeScript v5 as TypeScript v4 is significantly slower.

Features

Speed

This is likely not the fastest way to build a mono-repo. However, it is intended to be most stable. After constantly fighting against tsc's poor mono-repo tooling, and not desiring a full-blown mono-repo management tool (like Bazel) for simple projects, I finally built this.

Installation

npm i tsc-mono

Usage

It is recommended to first setup npm workspaces (if you use npm) as you must use package name imports to import between each in-repo TS project.

tsc-mono <command> <command-inputs>
  • <command>: the tsc-mono command you wish to run.
  • <command-inputs>: inputs to the tsc-mono command in the bullet above. Currently there is only one command: for-each.

for-each

for-each will run a given bash command for each TS project. The <command-inputs> are considered the bash command to run. Projects will be run in order based on their dependency graph.

Examples:

  • run type checking for each TS project:
    npx tsc-mono for-each tsc --noEmit
  • run "npm start" for each TS project:
    npx tsc-mono for-each npm start

Full Example

To see an example repo setup that this package works for, go to this package's test files: https://github.com/electrovir/tsc-mono/tree/main/test-files/augment-vir

Help output

Help message from the CLI:

tsc-mono usage:

tsc-mono <command> <command-inputs>

    - <command>: command that you want tsc-mono to run with this TS projects. Example: "for-each"
    - <command-inputs>: inputs for the given command. The options here will vary by command. Example: "npm run build"

Commands:

for-each
    - runs the given <command-inputs> as a bash script for each of the TS projects
    - projects are executed in dependency order

    Examples:
        - tsc-mono for-each npm run build
        - tsc-mono for-each "npm run build && echo success"