Import strategy in your main applications about cf-ui

[SpencerCDixon]

@tajo any thoughts? Also how do you guys do development of the components? Do you have a package that runs a webpack server to test everything out?

[tajo]

@SpencerCDixon

1. Not at all. Having a single entry point cf-ui would not scale when you start counting modules in hundreds. Various components can export Button without need to use some prefixes as DropdownButton, PaginationButton.

2. Yes!

3. You can place your application into the same yarn workspace as your UI kit. Everything gets symlinked. You can even take it a step further and alias all package imports through babel, so when you are deving, there is not difference between "main" code and UI kit code.

Also how do you guys do development of the components? Do you have a package that runs a webpack server to test everything out?

Yes, we have a special app that serves as a "canvas" for developing components in isolation. We also have a command to alias source of these components into our main application, so we can tweak it there as well.

[SpencerCDixon]

Sweeeeet, thank you for answering all my questions! I've been using this setup for the past couple months now and am really enjoying it. I've even been able to publish and reuse some form/util packages between web and react native.

The separate packages for importing has been pivotal for keeping bundle sizes small when code splitting!

Thanks again for the inspiration

Cheers 🍻

Edit: for others curious I set up styleguidist for component development/documentation and I have my web app in the packages dir as web and it's a private package