<div dir="ltr"><div>I fixed all the bugs in node-findit and submitted the patch to upstream: <a href="https://github.com/substack/node-findit/pull/34">https://github.com/substack/node-findit/pull/34</a></div><div><br></div><div>But I am afraid that upstream will not accept my code and I do not have time to wait. So I have forked findit to findit2 and started using that in my modules, because it fixes bugs.</div><div><br></div><div>So now my question is, when packaging these modules, may I update node-findit, keeping the same package name, but use my fork instead?</div><div><br></div><div>It keeps the same API and fixes all the findit bugs. Further, the only packages that depend on findit so far are mine:</div><div><br></div><div>$ apt-cache rdepends  node-findit</div><div>node-findit</div><div>Reverse Depends:</div><div> groovebasin</div><div><br></div><div>So far only groovebasin depends on node-findit. And this update happened upstream in groovebasin:</div><div><br></div><div><div>groovebasin</div><div> findit -> findit2</div><div> connect-static</div><div>  findit -> findit2</div><div> multiparty</div><div>  findit -> findit2</div></div><div><br></div><div>So that's 3 places that need the fork instead of the original, and 0 places that need the original.</div><div><br></div><div>What should I do?</div></div>