Testing the integrity of React components by publishing in a private registry
summary
Publishes components to a private Verdaccio registry, then runs Cypress end-to-end tests against a fresh install to catch missing files, wrong main/export entries, or broken transpile targets; Storybook pipeline boots the registry in about 5 seconds, caches published artifacts and tests across frameworks; real project data shows 70 packages with 54 published to validate the approach; demo repo and scripts automate init publish install build and test so failures surface before production with Verdaccio and Cypress end-to-end tests.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:31Package distribution basics
- 1:40Configuring package exports
- 2:57File inclusion strategies
- 4:22Common publishing pitfalls
- 5:43End-to-end testing strategies
- 7:02Verdaccio in CI workflows
- 9:16Advanced pipeline examples
- 11:48Hands-on implementation
- 14:37Q&A and closing
related talks
30mBuilding a Private React Component Gallery
32mKickstarting libraries of shared React components for multiple teams
34mI See What is Going on: Visual Testing for Your Components
19mWhy you should Jest use Cypress for React component testing
09mVisual Regression with Puppeteer, Playwright and Cypress
32mCrafting a Bulletproof testing pipeline for React Apps
33mKickstarting a library of internal React components for multiple teams
05mHow we have built a Node.js Registry with React