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

express-butterfly-effect

v1.0.6

Published

Compute the high-level endpoint impact of tiny code changes

Downloads

120

Readme

Express Butterfly Effect 🦋🌊

Descirption

When a butterfly flaps its wings over some line of your code there ~~is~~ was no telling of the consequence.

express-butterfly-effect takes one or more file changes and gives you back which express endpoints might be affected by those changes

Installation

npm i --save-dev express-butterfly-effect

Usage

You can either use express-butterfly-effect as a command-line app or as a library.

As a command-line app you would do:

./node_modules/.bin/express-butterfly-effect glob1 [glob2] change1 [change2]

You need to specify at least one glob and one change. Globs are used to find all the .js files in your project.

A change is a path to a file, followed by a : and then a line number or line range (start-count), possibly followed by other : plus line or range.

For example:

./node_modules/.bin/express-butterfly-effect './lib/**/*.js' \
  ./lib/my-file.js:1:4-2:10 \
  ./lib/my-other-file.js:5

# my-file.js changed at lines 1, 4, 5 and 10
# my-other-file.js changed at line 5

To use express-butterfly-effect you need to:

const computeEndpointImpact = require('express-butterfly-effect').default;
// Note: .default in the line above!

const impact = computeEndpointImpact(
  globs, // string[],
  targetFiles, // string[]
);

// impact is a string[], where each item looks like:
// 'get /api/users/1' (i.e. method + ' ' +  path)

Pulling changes from git

./node_modules/express-butterfly-effect/git-changes.sh [base-branch]

If you omit base-branch, the script defaults to master. This script returns the changes in the format you need to pass to express-butterfly-effect.

All together it would look something like:

./node_modules/.bin/express-butterfly-effect \
  './lib/**/*.js' \
  $(./node_modules/express-butterfly-effect/git-changes.sh)