Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow publishConfig.access to "public" even the package is not scoped #751

Open
fisker opened this issue Jul 16, 2024 · 1 comment
Open

Allow publishConfig.access to "public" even the package is not scoped #751

fisker opened this issue Jul 16, 2024 · 1 comment

Comments

@fisker
Copy link
Contributor

fisker commented Jul 16, 2024

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
@fisker
Copy link
Contributor Author

fisker commented Jul 16, 2024

This seems to happen due to my internet connection? Not sure..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fisker