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

jaybe78-babel-changed

v1.1.0

Published

Spawns babel with --only files modified since last run

Downloads

9

Readme

This runs babel on files that have been modified since the last run only, unless the last run failed (non-zero exit code) in which case the cache will not be reconciled and previously modified files will be re-transpiled (otherwise the cache reconcile will cause un-transpiled files to be missed if there is an error on a different file). It uses file-entry-cache. The first run will have no modification times saved yet so it will run on all files. Note: To delete the file stat cache so that the next run will include all files, use the command babel-changed --reset.

This is just an alternative to using --watch for weird people like me that never got in the habit of doing that.

Install

npm i -D babel-changed

Note: you will need to also install babel as per usual.

Usage

Note: I have tested this on my own computer with just my own simple babel command. Beyond that it may not work right, so YMMV.

Put something close to this in your scripts (note that the first argument is the source directory):

"build": "babel-changed src -d lib",
"clean": "babel-changed --reset"

Then, assuming babel, babelrc, plugins etc. are all set up, run:

npm run build

If there are modified files detected it will mention the number and pass a list of them as an --only option to babel. Otherwise it won't do anything. To rebuild everything next time, run npm run clean (no other arguments).

FYI, It spawns babel with pty.js. Also the file stat data is in node_modules/flat-cache/.cache/.