Daniel Schmidt

Interesting. Question is if it's a problem with the Intersection Observer API itself, in that specific browser.

Do you have time to debug this further? * Is the observer correctly triggered? https://github.com/thebuilder/react-intersection-observer/blob/master/src/observe.ts#L58 * Is `entry.isIntersecting` set to `true` when intersecting? * Is it something silly like the...

> I attempted to debug by creating a local copy of the `observe` function in [the fork](https://codesandbox.io/s/inview-plain-children-forked-ht4v9?file=/src/index.tsx) and using a Samsung Galaxy Tab 7 via Browserstack to view the console...

Is this still an issue?

Might you be able to solve this using a [type guard](https://www.typescriptlang.org/docs/handbook/2/narrowing.html#using-type-predicates)? Otherwise, how do you imagine the types being changed to support this pattern?

Suppose it could make sense to make some better type inference based on the type of `children`. It might also be solved if the type for `PlainChildrenProps` extends a `React.Component`,...

Right - all the more reason to have it switched to Emotion then. :)

Is there anyway of debugging `vitest` performance? Maybe list what takes time on each run, or which dependencies are loaded? After switching a React Testing Library application (built with Vite)...

Is it even possible to use testing-library and JSDom without `isolate: true`? You can't use `screen` to `getBy*` from the DOM since it will most likely contain multiple render outputs...

Might be worth looking at https://github.com/unjs/jiti - It's what Tailwind used to implement this for their [config file](https://tailwindcss.com/blog/tailwindcss-v3-3#esm-and-type-script-support) CJS/ESM/TS support.