Marius

Hi, looking at how linaria works I don't think this is possible with any reasonable amount of effort. Being a code-mod/-transform, linaria will replace ```css`...` ``` with a generated class...

I am afraid I don't understand the problem here. What is it you are trying to achieve/prevent? @zomem

Are you still trying to solve this issue @zomem ?

Hi, the issue seems to be a typing issue of `forwardRef`. Assigning the return-type of `forwardRef` to `StylableInputFwdRef` works: ```diff - const StylableInputFwdRef = forwardRef(({ label, className, style }, ref)...

There are two reasons why this doesn't work: 1. linaria works at _build-time_ and cannot interpolate _runtime_ styles. In React, component properties are unknown until runtime. 2. linaria does not...

Did this solve your issue? @meesfrenkelfrank

Hi, I had a similar requirement. [React's type declarations](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/2fe79f38fa0de0dc4778d37e03dbd61d2b90b9c5/types/react/index.d.ts#L2367) suggest extending the parent interface of `CSS.Properties`. If that doesn't work (as in my case) you can try augmenting react's `CSS.Properties`...

It seems you found a solution using patch-package @jalooc ?

@EdiAfremovFactify linaria's `styled` never returns a `ForwardRefExoticComponent` no matter the type of the component passed as its first argument. It is just missing a type signature handling that special case....

This is a possible duplicate of #1430. Have you tried the `tagResolver` option documented [here](https://github.com/callstack/linaria/blob/master/docs/CONFIGURATION.md)?