You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Already happened a few times that I found a name that seemingly is free, so showing a 404 on pubdev. I develop my package, polish it, get it ready for shipment. But when I try publishing, pubdev blocks it, because another package with a similar name already exists.
How am I supposed to know? "Rebranding" a package is not always easy. It would be very good if there was a way of checking avaliability. A small message on the 404 that reads along the lines of "did you mean xyz", or something integrated into the CLI, as described in dart-lang/pub#3966
The text was updated successfully, but these errors were encountered:
We could probably have a simple form that checks if the package name is available. As this is a server-side check specific to pub.dev (and may be absent on private or third-party servers), the pub client wouldn't know about it up until the actual publish attempt is made.
Already happened a few times that I found a name that seemingly is free, so showing a 404 on pubdev. I develop my package, polish it, get it ready for shipment. But when I try publishing, pubdev blocks it, because another package with a similar name already exists.
How am I supposed to know? "Rebranding" a package is not always easy. It would be very good if there was a way of checking avaliability. A small message on the 404 that reads along the lines of "did you mean xyz", or something integrated into the CLI, as described in dart-lang/pub#3966
The text was updated successfully, but these errors were encountered: