How we checked 20 PODIE installs with four package managers
On October 1, 2026, we checked 18 randomly selected components plus the CODING and DESIGN templates against the live podie.dev registry. npm, pnpm, Yarn and Bun each completed installation, TypeScript checking and a Vite production build.
What the test actually covered
We fixed the sample before running the checks. Each package manager received its own clean React project, and all 20 entries were installed together in that project using the real production URLs. This was four project-level integration checks, not 80 individually isolated application tests.
The projects used React and React DOM 19.2.6, Tailwind CSS 4.2.1, TypeScript 5.9.3 and Vite 8.0.13. The registry bytes for the sample matched the locally reviewed payloads; the two downloaded template ZIPs also matched and passed archive integrity checks.
A setup failure worth keeping in the record
The first Yarn run treated the temporary project as part of an enclosing workspace. We created an independent yarn.lock for the test fixture and reran it successfully. The product code did not change for that correction. Reporting only the final pass would hide a useful setup lesson.
Reproduce the workflow
Create a React TypeScript project using the official Vite and shadcn instructions. Configure Tailwind and the @/* alias, initialize components.json, then run the command from the selected component page. Use one package manager consistently in that project.
Import the component into a real page before running TypeScript and a production build. A successful registry request only proves that the payload can be downloaded; an unused import can also hide integration problems. The downloadable evidence below records the tested sample and payload hashes.
npx shadcn@latest add https://podie.dev/r/magicui--pulsating-button.json
npx tsc --noEmit
npm run buildWhat a pass does not establish
The checks do not prove that a user completed an installation, that every possible dependency combination works, or that the result is accessible and fast on every device. The sample does not establish Next.js compatibility. Verify your own framework, theme, keyboard paths and production page.
Copied source stays in your project. Upstream changes are not applied automatically. Review file differences and dependency changes before reinstalling or allowing an overwrite.
Related reading and evidence
Last updated: .