[DOCS] Plugin marketplace npm source docs are outdated for custom registry and version pinning support
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/plugin-marketplaces
Section/Topic
## Plugin sources documentation for npm source (package, version, registry) and implementation status notes.
Current Documentation
The page currently lists npm fields but still warns that npm sources are not fully implemented:
|npm| object |package,version?,registry?| Installed vianpm install|
and:
Plugin "x" uses npm source which is not yet fully implemented: usegithubor local path sources instead
What's Wrong or Missing?
Release v2.1.51 states:
Added support for custom npm registries and specific version pinning when installing plugins from npm sources
The docs still indicate npm source support is not fully implemented, and they do not provide concrete usage examples for:
- Custom npm registry configuration
- Explicit version pinning syntax
This is now outdated/conflicting guidance.
Suggested Improvement
Update plugin-marketplaces to:
- Remove or revise the "not yet fully implemented" npm warning if no longer accurate
- Add a complete npm source example using
package,version, andregistry - Document registry authentication expectations and fallback behavior
- Clarify any remaining limitations (if partial support still exists)
Impact
High - Prevents users from using a feature
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/plugin-marketplaces | npm source table and validation warning are inconsistent with new release behavior |
Total scope: 1 page affected
Source: Claude Code release v2.1.51
Changelog entry: "Added support for custom npm registries and specific version pinning when installing plugins from npm sources."
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗