> Yep, it'll break dependent installs, but that's the point: get dependents to move to the proper version. Probably more realistically, you'd put a note in you

> Yep, it'll break dependent installs, but that's the point: get dependents to move to the proper version. Probably more realistically, you'd put a note in your @delinka/ExcellentPackage repo readme saying that the package is deprecated and to use @fredralphbob/ExcellentPackage instead going forward, and simply not publish any more new versions. In fact I'm pretty sure npm has a built-in system to warn users of a package that its canonical name has changed.