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

quickfix

v1.0.4

Published

Detects and saves local changes to dependencies that are protected by .gitignore.

Downloads

20

Readme

Why?

You've worked 8,000 million-bazillion hours on 4 cups of coffee a minute trying to fix some stupid bug. It's 2am. If it's not fixed by morning Australia will cease to be a country.

You've found it. It's in a dependency of a dependency of a dependency. You've gone one too many layers deep. Making a mirror is gonna take too much time so you just edit the code directly.

You can't commit node_modules. Your code's gonna be deleted.

Poof. Gone. Never to be seen again.

but wait

But wait.

  • Wait
  • Wait
  • Wait

Hold up.

There's a stupid solution. An amazing, Australia-saving, stupid solution:

$ quickfix push

Quickfix will save your changes to a __quickfix__ folder, and then later you can run quickfix to update your node_modules with your 2am decisions once again.

Boom. Work saved.

Installation

Local (preferred)

$ yarn add --dev quickfix

Add npm-scripts and add quickfix as a postinstall hook in your package.json:

{
  "scripts": {
    "quickfix": "quickfix",
    "quickfix:push": "quickfix push",
    "postinstall": "quickfix"
  }
}

After making changes in node_modules run the command:

$ yarn quickfix:push

To update changes after installing a workspace using quickfix run:

$ yarn quickfix

Global

$ yarn global add quickfix

Add quickfix as a postinstall hook in your package.json:

{
  "postinstall": "quickfix"
}

After making changes in node_modules run the command:

$ quickfix push

To update changes after installing a workspace using quickfix run:

$ quickfix