The best stupid idea for fixing problems in node modules.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib
.gitignore
README.md
index.js
package.json
yarn.lock

README.md

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