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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ts-compile-checker

v1.0.19

Published

Checking that you can compile one or multiple of your typescript projects

Downloads

25

Readme

NPM! PRs welcome! Downloads License

Description

Managing a microservice architecture with multiple shared Typescript types quickly become cumbersome, if the compiler isn't watching the involed sub-projects.

This package solves those issues by:

  1. Recursively searching for tsconfig.json files in a specified directory
  2. Installing package.json dependencies
  3. Running the tsc compiler located in node_modules/.bin/tsc for each sub-project.

Usage

CLI

Npx

npx ts-compile-checker

Docker

docker run --rm -it -v $(pwd):/src:rw mkenney/npm:latest npx ts-compile-checker

Package.json script

{
  "dependencies": {
    "ts-compile-check": "^1.0.3",
  },
  "scripts": {
    "ts-compile-check": "node ts-compile-checker",
  }
}

Install and run

yarn add ts-compile-checker && yarn ts-compile-checker

Github Action

on: push
name: TS compilation check
jobs:
  checker:
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
      - run: npx ts-compile-checker
        working-directory: ./

Demo

Usage

Github Action

Options

| Flag | Type | Description | | ----------------- | ------- | ------------------------------------------------------------------------------------------------------- | | --help, -h | Boolean | Display this usage guide. | | --skip, -s | Boolean | Skipping the installation process. | | --include, -i | Array | Pass your own set of project paths. This will skip the search process. | | --exclude, -e | Array | Excluding a set of project paths. | | --options, -o | Array | Override the default options ["--noEmit", "--pretty"] passed to the tsc compiler for each sub-project | | --cwd, -c | String | Current working directory that the search process should be based on. Default directory is .. |

License

This project is licensed under the terms of the MIT license. See the LICENSE file.