Vojtech Miksu
Vojtech Miksu
@mxstbr @jaysoo Hey, I just published a tiny library [react-titled](https://github.com/tajo/react-titled) that supports more complex nesting. It uses the new context API that comes with React 16.3. You can use it...
We should also remove `create-react-context`, drop React
You should already see a warning describing this when Styletron context is missing due to multiple instances of React. Is there something else we could do?
Instead of `padding-left` you should use `padding-inline-start`. That's imo better approach than trying to programmatically switch styles. More info: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/RTL_Guidelines
You can always create some transformation function and use it in re-exports of `styled` or `useStyletron` APIs. I'm not sure if we want to add it into Styletron itself. In...
They started using `eval-source-map` for server side errors in this [PR](https://github.com/vercel/next.js/pull/13123/files) for performance reasons. You can fix things by adding `next.config.js` into your project and override their new defaults: ```js...
Yea, unfortunately this is still a problem with Next.js (including v10). They changed the source map format and [don't allow any customization](https://github.com/vercel/next.js/blob/canary/packages/next/build/webpack-config.ts#L1221). As @rtsao described that's not compatible with the...
Keeping the discussion about atomic `@supports` here. > First plain declarations, then @supports sorted by object key iteration order (yielding aqua in the above example) I don't think this would...
```js const aqua = { "@supports (color: yellow)": { color: "yellow" }, "@supports (color: aqua)": { color: "aqua" }, color: "red" }; const yellow = { "@supports (color: aqua)": {...
Quick workaround is to use `styletron-engine-monolithic` instead of `styletron-engine-atomic` since it doesn't use regexp based hydration. It seems that the regexp for keyframes doesn't really work properly. Trying to come...