Eetu Raunio

This seems to also happen with tsc and multiple @types library versions, with tsc always using the alphabetically first (older) @types library.

This seems like a regression that is affecting everyone with `testing-library/jest-dom` and using its functions. Edit: Seems like `@types/jest` has also regressed due to this and/or other changes when upgrading...

`ComponentChildren` is not necessarily one renderable value. It can be an array, and you cannot return multiple siblings without a parent node. It could also be a `string`, in which...

@lifeiscontent How do you suppose your element would work in JSX typing? Is the intended behaviour that when it is a child component it would understand that and would not...

Disabling CSS transforms by default on Firefox entirely seems like an overreaction, as they give a nice paint time benefit for non-SVG use-cases. Maybe a `console.warn` in development environments when...

This would be a great addition, and I have a use case for this in mind already. If this needs help (for example with reviewing), I'll gladly dedicate some time...

> @ConcernedHobbit does this help with the types issue [#5176 (comment)](https://github.com/pnpm/pnpm/issues/5176#issuecomment-1211238359)? Sure, this helps with jest and type issues, but then there's problems with developing component libraries using peerDependencies for...

> Looks like it works if I remove NODE_PATH from the command shim... And all tests seem to pass. But I am hesitant. It used to be required. > >...

> @ConcernedHobbit does this help with the types issue [#5176 (comment)](https://github.com/pnpm/pnpm/issues/5176#issuecomment-1211238359)? Dang, `@types/react` is breaking again. The weird error message may be a clue to what's going wrong. To recap,...

Related to #3685, the component does not blur correctly when tabbing out