-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Closed
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I'm running the following command:
publish --workspaces --access public
And I'm getting errors because it's trying to publish workspace packages that are marked as both private and restricted (I have an examples folder that is part of my workspace).
npm ERR! code EPRIVATE
npm ERR! This package has been marked as private
npm ERR! Remove the 'private' field from the package.json to publish it.
I believe this references #3231 @ruyadorno @wraithgar
Expected Behavior
It should respect the access controls.
Steps To Reproduce
- In this environment create two workspace packages and mark one as public and one as restricted (as well as include a
"private": true
- run
publish --workspaces --access public
- See error published above
For a real life example see this: https://github.com/exceptionless/Exceptionless.JavaScript/tree/f492ef2daf5c5930542e9b4ecc76dbcfd937488d
Environment
- OS: Ubuntu
- Node: latest (16.x)
- npm: latest (7.13)
Metadata
Metadata
Assignees
Labels
Bugthing that needs fixingthing that needs fixingPriority 1high priority issuehigh priority issueRelease 7.xwork is associated with a specific npm 7 releasework is associated with a specific npm 7 release