np
np copied to clipboard
Allow `publishConfig.access` to "public" even the package is not scoped
Description
Similar to #749, I don't want different publishConfig in my packages, putting "access": "public" is not harmful.
Is the feature request related to a problem?
Possible implementation
Skip check when publishConfig.access is "public"
Alternatives
This seems to happen due to my internet connection? Not sure..