Shu Ding
Shu Ding
There are some cases where a CSS rule is used for compatibility reason like `-webkit-*` (the component can be used by both Satori and Next.js). But I think it should...
@transitive-bullshit Are you using Tailwind mode or just the normal style prop?
Thanks for the great feedback @transitive-bullshit! I think most of these can be improved in future updates.
It's interesting that gap already works, because that WASM build is based on an old commit that probably doesn't have gap... I'll figure out why...
Released all the changes in `yoga-wasm-web`, but currently the blocker is that we need to fork https://github.com/vadimdemedes/yoga-layout-prebuilt to make it stick to the same commit of Yoga.
Yeah ideally we should maintain a newer version. Previously I compiled `yoga-wasm-web` with latest Yoga but it introduced a strange bug with `position: absolute`, which doesn't happen in older versions...
That looks like the same one as #185, I think we can add something to our build script to work around it.
About `text-align: center`, that’s because every container is a flexbox and that matches the spec. You can compare it with the “HTML” result to confirm. To center the content you...
Good call, I think it should preserve `id`, `class` and `data-*` attributes. There's some work to be done for this because it's not a 1:1 mapping between DOM/SVG elements, e.g....
`useSWR` is client only and cannot be used in server components. You can add `"use client"` on the top of your page file to convert it to a client component.