Mihkel Eidast
Mihkel Eidast
Hi @LukeChannings! First of all, thanks for this example repository! I've been trying to figure out how to setup a tree-shakeable component library, so this definitely helped out. I wanted...
Context: I have a quite large monorepo that has a lot of nested and symlinked node_modules directories. For a better visualized example, look at this file tree: ``` shared module_a...
### Context - If some other dependency has a similar implementation of useId that only returns an incremented number, these IDs can conflict. - Number-only ID-s are hard to read...
**Describe the bug** After updating from `zenika/alpine-chrome:80` to a newer version (I've tried both `zenika/alpine-chrome:81` and `zenika/alpine-chrome:89` and both fail, `zenika/alpine-chrome:77` and `zenika/alpine-chrome:80` behave as expected), default fonts are not...
Hey! Thanks again for this project. I'm currently setting up Playroom for a project that has multiple themes. From the current docs, it's quite difficult to grasp exactly what needs...
Our library exports some helper functions in addition to React components. Playroom does not look at what is exported and adds everything to suggestions:  Two possible solutions I see...
First, a big thank you for this module. It's really helped out a lot over the years. An issue rose from the last minor update: > Fixed: Compositing issues in...
The examples are unclear on why it works that way. Mutating params feels wrong, because in the code it is not very easy to understand how my empty keys array...
Split out from https://github.com/floating-ui/floating-ui/issues/1807 The current global solution for disabling pointer-events is flaky, some issues raised in that linked ticket: > We are still running into issues in automated browser...
**Describe the bug** When setting EmptyPlaceholder to a custom component, it is rendered inside the `` element. This is wrong for two reasons: 1. Semantically, I believe this is incorrect....