Closed claireolmstead closed 4 weeks ago
Great work!
Am I right in assuming that a consumer of the package would not be interested in the Storybook UI (that's more for exploring the styles in this repo)? And that the consumer is really mostly interested in the base component/color/font definitions? If that's true, it might be best to separate that out into separate packages, so that the published package only contains the core components and not the Storybook UI. Take a look at the SIWF repository; that's also a Vite/Svelte project with separate packages; some of which are published & some that aren't.
If that's the route we think we want to go, I'd be okay with merging this & make that the subject of a subsequent issue/PR.
Great work!
Am I right in assuming that a consumer of the package would not be interested in the Storybook UI (that's more for exploring the styles in this repo)? And that the consumer is really mostly interested in the base component/color/font definitions? If that's true, it might be best to separate that out into separate packages, so that the published package only contains the core components and not the Storybook UI. Take a look at the SIWF repository; that's also a Vite/Svelte project with separate packages; some of which are published & some that aren't.
If that's the route we think we want to go, I'd be okay with merging this & make that the subject of a subsequent issue/PR.
Linked to #13
Goal
The goal of this PR is to create a package we can release to setup the basics of our style guide.
Closes #1
Discussion
Currently the components are loading into /src in the package, so you have to reference that path when importing a component. Is there a way to avoid that?
Checklist
How To Test the Changes