-
Notifications
You must be signed in to change notification settings - Fork 0
npm: publish as scoped @your_conscience/dotagents #149
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| { | ||
| "name": "dotagents", | ||
| "name": "@your_conscience/dotagents", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
After this rename, two user-facing commands still target the unscoped package: AGENTS.md reference: AGENTS.md:L50-L50 Useful? React with 👍 / 👎. |
||
| "version": "0.0.0-dev", | ||
| "description": "Dotfiles for your AI agents: one ~/.agents repo synced to every coding agent.", | ||
| "license": "MIT", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue (broader_impact): After the package is renamed to
@your_conscience/dotagents, the CLI's postinstall recovery message still instructs users to runnpm rebuild -g dotagents; that command targets the old unscoped package and does not reliably rebuild the installed scoped package.Triggers: When the postinstall download fails or the installed binary is missing.
Suggested fix: Update the recovery command to
npm rebuild -g @your_conscience/dotagentsand update any other user-facing references to the old package name.