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

build-if-changed

v1.5.5

Published

Run build scripts only when files changed

Downloads

4,697

Readme

build-if-changed

Build your packages only if they changed since the last build.

 

How it works

  1. Look for package.json modules in the working directory, ignoring any node_modules directories by default. Any local .gitignore is also respected.

  2. Crawl the package and generate SHA-1 hashes from every watched file. These hashes are stored in the .bic_cache file next to each package.json module.

  3. If any .bic_cache files are outdated, then bic will execute npm run build in the relevant packages.

 

Usage

  1. Install the package:
yarn add build-if-changed -D
  1. Edit your package.json module to customize the behavior:
// Only watch the "src" directory:
"bic": ["src"],
// Any glob can be included or excluded:
"bic": { "only": [], "skip": [] },
// Disable bic for a package:
"bic": false,
  1. Use the package:
yarn build-if-changed
# or
yarn bic

 

Notes

  • The skip config takes precedence over the only config.
  • The .git and node_modules directories are always skipped.
  • Any package with bic or build-if-changed in its "build" script is skipped.
  • This tool uses a custom glob syntax (see here).