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

@qatonda/tsc-run-scripts-hook

v1.1.3

Published

This is a package that will run configured npm scripts after `tsc` is run. It will even follow project references in your `tsconfig.json` to run their scripts.

Downloads

1

Readme

tsc-run-scripts-hook

This is a package that will run configured npm scripts after tsc is run. It will even follow project references in your tsconfig.json to run their scripts.

when does this run

We only run scripts under the following conditions:

  • the args aren't present: -h, --help, -all, --clean
  • and if the tsc process exits successfully (0)

The npm scripts will be run as the tsc process exits.

examples

copy files

Say you want to be able to copy all non-{ts,js} files after typescript builds. You would use the following tsconfig.json:

tsconfig.json

{
  "compilerOptions": { ... },
  "run-scripts": ["build-step:copy-files"]
}

package.json

{
  "scripts": {
    "build-step:copy-files": "copyfiles -u 1 src/**/*.{json,html} dist/",
  },
  ...
  "devDependencies": {
    "copyfiles": "*",
  }
}

This would be equivalent to the following when running $ tsc ....

$ tsc [-b] # or whatever you use to build
$ npm run build-step:copy-files
| $ copyfiles ...

copy files with project references

Say you want to be able to copy all non-{ts,js} files after typescript builds and you had more than one project in your repo that you defined using tsconfig.json's references field. You would use the following layout:

project-a/tsconfig.json

{
  "compilerOptions": { ... },
  "run-scripts": ["build-step:copy-files"],
  "references": [
    { "path": "project-b" }
  ]
}

project-a/package.json

{
  "scripts": {
    "build-step:copy-files": "copyfiles -u 1 src/**/*.{json,html} dist/",
  },
  ...
}

project-b/tsconfig.json

{
  "compilerOptions": { ... },
  "run-scripts": ["build-step:copy-files"]
}

project-b/package.json

{
  "scripts": {
    "build-step:copy-files": "copyfiles -u 1 src/**/*.{json,html} dist/",
  },
  ...
}

This would be equivalent to the following when running $ tsc ....

[project-a] $ tsc -b
[project-b] $ npm run build-step:copy-files
[project-b] | $ copyfiles ...
[project-a] $ npm run build-step:copy-files
[project-a] | $ copyfiles ...

tsconfig.json: project references

This is particularly helpful in situations with a monorepo and configured tsconfig project references. By default without this project, it will compile the references, but not run scripts! This is where tsc-run-scripts-hook comes in handy. It's a lightweight project meant to run npm scripts post build.