Mateusz Burzyński

> Runners are generally a better fit for files that a processed in isolation (like tests, linting, and babel's transpilation) rather than something that needs the whole thing in memory...

> We have a JEST_WORKER_ID env variable. You could also make some custom watch plugin or reporter to hook into some lifecycle telling you "new run". Does that cover it?...

Sorry, I've missed that discussion. I see the points raised there but having to cast this through unknown/any first and then to `SVGElement` doesn't seem like a good DX. I...

@orta where such a FAQ should live in? this repo? main TS docs?

I've just been hit by this myself and I've wanted to fix this here. Since the types are generated I'm unsure where this alias originates and I'm unsure how I...

Why would you like to use `props.style.height`? This is being controlled by the `react-textarea-autosize` because it's the only way to implement "autosizing". I don't believe that you should ever pass...

Could you prepare a repro case on which I could take a loot at?

Just a note - I've recognized a problem on CodeSandbox using your provided repro https://github.com/codesandbox/codesandbox-client/issues/4307 I've also checked that those 2 are not the same: ```ts type Ref1 = React.ComponentProps["ref"]...

Actually - I have gone in a slightly different direction. You can take a look at https://github.com/Andarist/react-textarea-autosize/commit/db872f035e8c033eb96c40eead9c041ec6b2e09f . I will probably release this over the weekend.

> I'm not exactly sure why JSX.IntrinsicElements['textarea'] and React.TextareaHTMLAttributes use different ref types I don't think this is a problem. The problem is that I've declared our props to use...