top | item 18688716

(no title)

perpetualcrayon | 7 years ago

I'd say force a fork there too. It's not difficult to switch to a new package once you find it and know the URL. I say force each user (whether it's end user or library maintainer) to switch manually to the new maintainer's fork of your project.

"I have not looked at the readme...". Maybe this will create a market for a new type of project. The one that lets folks know the status of the packages they use in their project.

discuss

order

mcguire|7 years ago

jquery, jquery-forked, new-jquery, forked-jquery, my-jquery, this-is-the-real-jquery, potato-headed-rat-bastard-jquery, ...

Klathmon|7 years ago

npm has scoped packages, so you could make @mcguire/jQuery and I could make @klathmon/jQuery