What are the challenges in getting Atmosphere packages to npmjs.org and how can we solve them? For both MDG to work out what's needed in tooling and for eventual good docs for the community package authors.
Gadi CIt was mentioned by MDG back on the 0.9 rc's, but never landed :> I thought it might be helpful to put in one place exactly what work would be required here. The basics are:
Allow account rename and/or transfer of ownership
Redirect queries from the old name to the new name
This means that if the user `gadicohen` is renamed to `gadicc`, requests for`gadicohen:famous-views` will automatically fetch `gadicc:famous-views`, handle version solving, etc. Essentially alias support.
Create a new account
Inform your users of the upcoming change
Create a new package that `imply`'s your old package
Users won't get updates on the new package
Cons with this approach:
Confusion with multiple similarly named packages and their different versions