Closed VanishMax closed 2 weeks ago
Latest commit: 4e49ce9fd67a6a0e716fcf60f106ba56eb85965a
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
@grod220 do you have the idea why the tests are failing in the minifront? Seems like it is triggered by your changes
https://github.com/penumbra-zone/web/actions/runs/11724483746/job/32658624212?pr=1891
The "multiple copies of react" issue sounds like you are bundling react with the tailwind package. Think that means you need to make it a peerDep and not a main dependency.
Followed up by https://github.com/penumbra-zone/web/pull/1902
The Tailwind-based UI library.
Vite, in this case, builds the library code and produces simple JavaScript that takes React's
createElement
and applies the right classes to it. The styling responsibility for now is on the consumer's side. However, I exported one function for simple Tailwind configuration of consumer'stailwind.config.ts
:Components list. Agenda: ✅ – implemented, 🟡 – not implemented (not needed for now), ❌ – i decided not to implement it.
Future work
withPenumbra
hook to cover all config merging cases.css
file with all compiled Tailwind classes, so consumers wouldn't need Tailwind in their projects