Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: should not throw in React 19 #32

Merged
merged 12 commits into from
May 28, 2024
Merged

fix: should not throw in React 19 #32

merged 12 commits into from
May 28, 2024

Conversation

ling1726
Copy link
Member

React internals have been moved around in v19. This PR adds the React 19 internals path as a fallback.

Also updates CI to test on React 19 and adds utility to exclude tests that still fail in 19

Fixes partially #31

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 3.2.8 to 3.2.10.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v3.2.10/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v3.2.10/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
describe("useDisposable", () => {
describe("in strict mode", () => {
it("should not call strict effect or memo", () => {
const factory = vi.fn().mockReturnValue(["foo", vi.fn()]);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in React 16 and 17 it's actually Ok for useMemo/useState to run twice. In these cases it's more worthwhile to test that use-disposable does not detect StrictMode at all

@ling1726 ling1726 merged commit fde0f71 into main May 28, 2024
6 checks passed
@ling1726 ling1726 deleted the fix/react-19-throw branch May 28, 2024 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants