I’m aware that npm package names should be all-lowercase, and it seems up until now Unity has been silently ignoring packages that have uppercase letters in their identifier. However, starting with this alpha connecting to a scoped-registry with any packages that have uppercase identifiers causes the entire package manager to refuse to refresh with the following errors:
Errors
[Package Manager Window] Cannot perform upm operation: Unable to perform online search:
Package name ‘’ is invalid. [InvalidParameter].
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
Is this a Bug that is expected to be fixed, or the new defined behavior? I ask because we have a scoped registry we connect to that has uppercase packages published, and it would prevent use of the package manager. Obviously the best solution would be to remove all offending packages, but want to avoid a situation where the package manager is brought down for everybody any time a new uppercase-letter package is accidentally published.
Thanks for bringing this up to our attention. It’s most definitely a bug! You’re absolutely right in expecting the package manager to not require absolute perfection of every package on the registry, this would result in an increased risk, scaling up with the amount of content on the registry. You can track this issue on the Issue Tracker.