Skip to content

chore(release): scope npm package as @seanpk/markupit - #10

Merged
seanpk merged 1 commit into
masterfrom
chore/scope-to-seanpk
Jun 16, 2026
Merged

seanpk merged 1 commit into
masterfrom
chore/scope-to-seanpk

Conversation

@seanpk

@seanpk seanpk commented Jun 16, 2026

Copy link
Copy Markdown
Owner

The unscoped name markupit is blocked by npm's name-similarity guard (too close to the existing markup-it), so we publish under the personal scope @seanpk/markupit.

Scoping sidesteps the similarity check, and the CLI command/bin stays markupit — only the installed/npx package name changes.

  • package.json name → @seanpk/markupit
  • README quickstart/usage → npx @seanpk/markupit (+ a note that a global install gives the bare markupit command)
  • docs (REQUIREMENTS CLI-1, UX-CHECKLIST) → scoped invocation

No behavior change; the published bin and overlay are identical. First publish will use npm publish --access public.

🤖 Generated with Claude Code

The unscoped name `markupit` is blocked by npm's name-similarity guard
(too close to the existing `markup-it`). Publish under the personal
scope instead. The CLI command and bin stay `markupit`; only the
installed/`npx` package name changes.

- package.json name -> @seanpk/markupit
- README quickstart/usage -> `npx @seanpk/markupit` (+ global-install note)
- docs (REQUIREMENTS CLI-1, UX-CHECKLIST) -> scoped invocation

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@seanpk
seanpk merged commit fa74cd1 into master Jun 16, 2026
4 checks passed
@seanpk
seanpk deleted the chore/scope-to-seanpk branch June 16, 2026 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant