Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[React Widget][Part 1] bare-bones skeleton #277

Closed
wants to merge 3 commits into from
Closed

Conversation

donyu
Copy link
Collaborator

@donyu donyu commented May 29, 2024

The way I've widgetized UIs into npm packages the past is as follows:

  1. Create a directory for the new widget package code with a bare skeleton and start using that skeleton in the production app. In this case I've named it ibcfun.js.
  2. Start migrating UI and business logic into the new widget package. I typically like to start top-down through the react hierarchy. This is also a good time to increase test coverage as you migrate. I'd set up storybook to test out the widget standalone.
  3. At each point, update the imports in the production app and make sure that the widget works and can replace the production app contents.
  4. At the end, the original project should be a 1st class consumer of the widget npm package.

@donyu donyu requested a review from bpiv400 as a code owner May 29, 2024 17:54
Copy link

vercel bot commented May 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
ibc-dot-fun ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 29, 2024 6:11pm

@donyu donyu requested a review from codingki May 29, 2024 17:54
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