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 🙏

© 2025 – Pkg Stats / Ryan Hefner

tscfc

v1.5.0

Published

CLI utility for incrementally converting projects to TypeScript or applying new rules.

Downloads

180

Readme

Tsconf Files Checker

A small CLI utility that helps with incrementally converting your project to TypeScript or to incrementally apply new rules (strictNullChecks, noImplicitAny, etc.) to an existing TypeScript project.

Flow

  1. The first tscfc run will output files without errors.
  2. Command tscfc --update includes files without errors to tsconfig.
  3. After that, each tscfc --update checks files against tsconfig files (from step 2) and shows the user if anything is broken:
    • If there are files without errors, tscfc will include them in tsconfig.
    • If there are broken files (files that are already in tsconfig have errors), it will output errors and exit with code 1 (fail tests).

Installation

npm i -D tscfc

Example

Run from the terminal:

Usage: tscfc --project TSCONFIG_PATH SRC_PATH

Example: tscfc ./index.ts --project ../App/tsconfig.strict.json ../App/src

        --project       Path to your tsconfig.json
        --verbose       Print all logs, useful for debugging
        --update        Include successful files to tsconfig
        --remaining     Print all remaining files

Note: In order to check JavaScript files, please include allowJs: true in tsconfig.

Recommended Settings

If you want to incrementally enforce some rules (e.g., noImplicitAny, strictNullChecks), create tsconfig.strict.json alongside your tsconfig.json. Then add to tsconfig.strict.json:

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "noImplicitAny": true,
    "strictNullChecks": true
  }
}

In package.json, add a pretest script, which will automatically run before your tests to check if you broke something or not, even before the test.

{
  "scripts": {
    "pretest": "tscfc --project ./tsconfig.strict.json ./src"
  }
}