Jakob Guddas

@ad1992 you are 100% right. I don't have a solution how to correctly map the keys for cases where we use option, do you have any suggestions? If not, let...

I reverted the 6 option keybindings back to use the old `event.code` behavior, this should all work now.

+1 for not adding this. If people really want this, they can add their own `unsafe` validator like this: ```ts const unsafe = () => ({ parse: (v: unknown) =>...

https://github.com/jguddas/vim-lightscript its still quite rudimentary :smile:

I prefer `@xstyled/styled-components/native` over `@xstyled/styled-components-native` due to all the duplication. Maybe there is a way to trim this down and get rid of the dependency for react-native itself?

@ad1992, can you take a look again, this is in a mergable state afaik.

Can you share an example where overriding does not work? Doing it like [this](https://stackblitz.com/edit/react-ts-fwfl8g?file=App.tsx) for example works just fine.

I'm a big fan of having a utility that behaves similarly to `styled(MyComponent)` from `styled-components`. ```ts interface ButtonProps { children: React.ReactNode; } const Button = styled(x.button, { type: 'button', color:...

My guess would be that this is due to the cache continuously growing.

I was able to reproduce this with Next.JS, the way to fix it for me here was like this: ```diff import { x, ThemeProvider } from '@xstyled/styled-components' + const theme...