Daniel Schmidt

Fixed in #701

Can you verify that it's 9.12 it first happens? What if you run just one test? It could be Jest resets the observer after a run, so before All isn't...

Could be a difference between vitest and jest, and how they reset code. Might have to go back to beforeEach for Jest tests then.

I've tried installing and running the `hooks.test.tsx` tests using Jest instead of Vitest - Using a default Jest configuration, it correctly does the mocking, so `mockAllIsIntersecting` works as expected. ![CleanShot...

@julian-jambit that could explain the issue. This change was made because of the issue in #689 - I'm thinking it might sense to just go back to `beforeEach` to be...

:tada: This issue has been resolved in version 9.15.0 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/react-intersection-observer/v/9.15.0) - [GitHub release](https://github.com/thebuilder/react-intersection-observer/releases/tag/v9.15.0) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Right. Okay. I should be able to determine the mock state without using a variable.

@julian-jambit could you try https://github.com/thebuilder/react-intersection-observer/pull/716 - You should be able to install it before it's released with the pkg-pr-new bundle: ```sh npm i https://pkg.pr.new/thebuilder/react-intersection-observer@716 ```

Jeez, what kind of pseudo reset is that. Seems like Vitest does the same. Can't find an obvious way to determine if it has been reset. Maybe I have to...

:tada: This issue has been resolved in version 9.15.1 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/react-intersection-observer/v/9.15.1) - [GitHub release](https://github.com/thebuilder/react-intersection-observer/releases/tag/v9.15.1) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket: