![]() (And it just so happens to align with with everything we’ve talked about so far.) I like what Leonardo Losoviz has to say about the monorepo approach. In AgnosticUI, for example, I’m currently using Storybook and often kick off all the framework Storybooks, or run snapshot testing across the entire monorepo. As this sort of project grows, it’s safe to assume there will be more proper testing. We want the convenience of firing up all four button implementations at the same time for testing. Ideally, we’d like to correct things in one place rather than making individual fixes in separate repositories. Let’s say the button needs a tweak - like the “focus-ring” implementation, or we screwed up the use of aria in the component templates. A monorepo setup provides a convenient structure that facilitates copying our single button.css component into various framework-based projects. So, by nature, there’s some purposeful coupling going on between the various framework implementations and the single-source-of-truth CSS file. We’re trying to build a single button component that uses just one button.css file across multiple frameworks. But here’s my own biased list of benefits that I feel are relevant for our little buttons endeavor: Coupling Why? Chris actually has a nice outline of the benefits in another post. ![]() We’re going to set up a tiny Yarn workspaces-based monorepo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |