Pain Point: redirecting deprecated packages

[stefee]

Let's use joi package as an example, where @hapi/joi was deprecated in favour of joi. The last version of @hapi/joi was v17.1.1, and any future versions of the package are published to joi.

Ideally, querying the registry to see which versions of @hapi/joi are available would tell you about the new versions of joi so that dependency bots would be able to do the switch to the new package name, and running npm install @hapi/[email protected] on the command line would spit out a warning and install [email protected] instead.

Currently, dependency bots have no idea about the new versions, so the dependency just goes stale over time unless an engineer is told directly via email or twitter or something to go in and manually update the dependency.