search

Manishearth / namespacing-rfc

RFC for Packages as Optional Namespaces
47 stars 3 forks source link

Drawback: Slow migration #5

Open Manishearth opened 4 years ago

Manishearth commented 4 years ago

The RFC as currently written provides a less-than-ideal migration path:

Existing projects wishing to use this may need to manually migrate. For example, unic-langid may become unic/langid, with the unic project maintaining unic-langid as a reexport crate with the same version number. Getting people to migrate might be a bit of work, and furthermore maintaining a reexport crate during the (potentially long) transition period will also be some work. Of course, there is no obligation to maintain a transition crate, but users will stop getting updates if you don't.

A possible path forward is to enable people to register aliases, i.e. unic/langid is an alias for unic-langid.

pksunkara commented 4 years ago

I would definitely support aliases and it neatly fixes this problem. There are so many times where I wished npm has aliases so that we could probably migrate stuff for http://storybooks.js.org