walter-base/common-workflow
1
0
Fork 0
mirror of https://github.com/walter-base/common-workflow.git synced 2026-09-08 19:26:46 -04:00
Code Issues Packages Projects Releases Wiki Activity

docs: correct npm scope guidance

Browse Source 
The scope routes installs to the registry via .npmrc; it does not have to
match the registry owner. Gitea's own example maps an `@test` scope to a
`testuser` registry URL.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Jm9AfbCJBD4tkxnxxnq7Wm
This commit is contained in:
Walter Cheng
2026-07-26 14:18:19 -04:00
co-authored by Claude Opus 5
parent 936760d68f
commit c33db49634
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -1
View File
@@ -55,7 +55,9 @@ Notes:
the two can never drift apart
- `package.json` is generated at publish time with the release version, which
keeps it in step with the plugin manifest versions that release-please bumps
- `npm_package_name` must be scoped, and the scope must match the registry owner
- `npm_package_name` must be scoped, because the scope is what routes installs to
the registry in `.npmrc`. The scope does not have to match the registry owner:
Gitea's own example maps an `@test` scope to a `testuser` registry URL
- `NPM_TOKEN` is used when set; otherwise `GITEA_TOKEN` is reused
- publishing fails if any released path is absent from the packed tarball, which
guards against npm's ignore rules silently dropping `.agents/` or