Skip to content

Call the unscoped cap2ui5 a deprecated placeholder, not withdrawn - #33

Closed
oblomov-dev wants to merge 2 commits into
mainfrom
claude/cap2ui5-moved-notice
Closed

oblomov-dev wants to merge 2 commits into
mainfrom
claude/cap2ui5-moved-notice

Conversation

@oblomov-dev

@oblomov-dev oblomov-dev commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

The site says the unscoped cap2ui5 is "withdrawn from npm". Since 2026-09-30 04:17 UTC that is no longer true: cap2ui5@0.0.1-placeholder is on npm, latest and deprecated.

What the placeholder is (read from the published tarball): no main, and a cap2ui5 bin (index.js) that prints "This name is a placeholder. The package is @cap2ui5/cds-plugin …" to stderr and sets exit code 1. It installs nothing an app can use. The first version of this PR was written for a planned cap2ui5@0.1.1 notice whose require would throw. That is not what was published, so the second commit describes the placeholder instead and no longer claims that requiring it throws.

What changes

  • docs/guide/ecosystem.md and the quickstart's "Coming from the package cap2ui5" box: cap2ui5 is a deprecated placeholder that installs nothing usable. The swap command npm rm cap2ui5 && npm add @cap2ui5/cds-plugin stays.
  • AGENTS.md: the ground truth (cap2ui5@0.0.1-placeholder, what it contains) and the verify-refs description.
  • scripts/verify-refs.mjs: comments and messages only. It still reports an import or dependency on cap2ui5.
  • Left alone: the dated note at the top of HANDOVER.md, which records the state on 2026-09-29.

Checks

npm run check: verify-refs OK, build OK.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NwpbkojNzGmuJrFdbwo5JF

The unscoped package cap2ui5 was unpublished with 0.3.0, and the site said it
is withdrawn from npm. It is being published again as cap2ui5@0.1.1, a
deprecated notice: requiring it throws an error that names
@cap2ui5/cds-plugin, and its cap2ui5 bin exits with the same pointer. The
ecosystem page, the quickstart's "Coming from the package cap2ui5" box,
AGENTS.md and verify-refs' comments and messages now say that. What the
checker reports is unchanged: an import or dependency of cap2ui5 still
installs nothing a reader can use.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NwpbkojNzGmuJrFdbwo5JF
What was published under the unscoped name on 2026-09-30 is
cap2ui5@0.0.1-placeholder, not the notice package this PR was written for:
no main and no throw - its cap2ui5 bin prints where to go and exits 1. The
pages no longer claim that requiring it throws an error; they say it is a
deprecated placeholder that installs nothing usable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NwpbkojNzGmuJrFdbwo5JF
@oblomov-dev oblomov-dev changed the title Call the unscoped cap2ui5 a deprecated notice, not withdrawn Call the unscoped cap2ui5 a deprecated placeholder, not withdrawn Sep 30, 2026

Copy link
Copy Markdown
Member Author

Superseded by #36. It carries the same placeholder wording, applied on top of #35, together with the update to 0.4.0.


Generated by Claude Code

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.

2 participants