Measured entry

magicui-client-tweet-card

cardbento

A client-rendered tweet wrapper shipped as a shadcn registry component. It uses react-tweet to fetch tweet data, then delegates loading, error, and finished rendering to a separate local tweet-card module. That companion module is referenced through a project alias but is not included in this registry item, so the verified build cannot resolve it.

Specimen
Harness screenshot of magicui-client-tweet-card at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-client-tweet-card at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of magicui-client-tweet-card at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for magicui-client-tweet-card
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal35.3 KB (100.7 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 25.39s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/tweet-card.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

Do not publish this as a working standalone component. The registry payload omits the local tweet-card module it imports, so the build fails before mounting. It needs a shadcn-style setup plus the companion Magic UI tweet-card implementation.

Use it if

  • You already have Magic UI's companion tweet-card module installed at the expected alias.
  • You need client-side tweet fetching with replaceable loading and not-found states.
  • You are prepared to maintain a live social embed and its network-dependent failure handling.

Skip it if

  • You need a standalone registry item that builds immediately after installation.
  • Your project does not use shadcn-style aliases and you do not want to rewrite its imports.
  • You cannot add the omitted MagicTweet, TweetSkeleton, and TweetNotFound implementation.
  • You prefer server-rendered or static tweet content without a client fetch.

Install

Installation record for magicui-client-tweet-card
Declared dependenciesreact-tweet
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

Install react-tweet, add the companion Magic UI tweet-card module with its own styles and utility dependencies, and configure the project alias used by the import. In a non-shadcn project, rewrite that alias to a valid relative path and ensure the file exports MagicTweet, TweetSkeleton, and TweetNotFound.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

License
MIT
Record published
2026-08-13

Alternatives

Other published entries for the card pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.