I often find myself in a situation where the npm package does exactly what I need, but has an error or missing function that blocks me from using it directly. So I divorce him and make a pull request with what I need.
The problem occurs when the accompanying package is too busy to integrate my PR, so I just got stuck with the plug. I cannot have a point of project dependency on the gifub repo fork, since the npm package usually has some kind of compilation / forwarding step. I can publish the plug under the new package name, but then I have to support it.
Is there a better way to use my package plug?
(To clarify, I don’t want to use npm link for development. I want the package to be listed constantly so that anyone else can clone my project and run npm install to make it work.)
source share