Inconsistency about organizations and unscoped packages
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 711
- Forks
- 4.2k
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 3
Description
https://docs.npmjs.com/package-scope-access-level-and-visibility
Note: Only user accounts can create and manage unscoped packages. Organizations can only manage scoped packages.
https://docs.npmjs.com/about-organization-scopes-and-packages
While you are granted a scope by default when you create an organization, you can also use organizations to manage unscoped packages, or packages under a different scope (such as a user scope).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the statements in “Package scope, access level, and visibility” and “About organization scopes and packages,” linked in the issue. Confirm the intended organization behavior from the surrounding documentation, then update the conflicting wording so both pages agree and verify the rendered MDX documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100