Proper fork workflow for a node module repo that does'nt want to merge your perfectly fine pull request.

proper-fork-node.md

Fork it

Clone your fork :

git clone [email protected]:YOU/FORK

Add the original repo as an remote :

git remote add upstream [email protected]:HIM/BASE

Change it

Hack away.

You can also merge other pull requests. First get the pull request ID from the original repo and then pull :

git pull [email protected]:HIM/BASE/refs/pull/153/head

Branch it

To avoid publishing on npm, branch with a name referencing the original module version :

git checkout -b 1.1.0-a

Build it

• In .gitignore, remove lines referring to the build folder (e.g. dist or build).
• Build the project (e.g. npm run build).
• Check that package.json has a main property linking to the build entry point (e.g. dist/index.js).

Use it

In your app's package.json, assign the branch of your fork instead of the usual npm version :

{
  "dependencies": {
    "module": "YOU/FORK#1.1.0-a"
  }
}

Sync it

git fetch upstream
git checkout master
git merge upstream/master

Then branch it, build it, use it again.