[dependabot]

Bumps @react-three/fiber from 9.0.4 to 9.8.1.

Release notes

Sourced from @​react-three/fiber's releases.

v9.8.1

The main changes here are bug fixes:

• Activity now works completely inside of R3F, even across boundaries with React DOM. Ie, an Activity that wraps the Canvas.
• In some cases a renderer would not be disposed when the Canvas was unmounted. This is fixed and we clarify in which instances we auto-dispose.

What's Changed

• fix(core): dispose the renderer R3F creates when its root unmounts by @​tonyblu331 in pmndrs/react-three-fiber#3942
• fix(core): preserve visibility across Activity and Suspense hiding by @​krispya in pmndrs/react-three-fiber#3944
• fix(web): keep a Canvas root alive while hides it by @​tonyblu331 in pmndrs/react-three-fiber#3943
• fix(core): stop Canvas rerenders from resetting runtime settings by @​krispya in pmndrs/react-three-fiber#3945
• fix(core): bridge Activity visibility into Canvas scenes by @​krispya in pmndrs/react-three-fiber#3946

New Contributors

• @​tonyblu331 made their first contribution in pmndrs/react-three-fiber#3942

Full Changelog: pmndrs/react-three-fiber@v9.8.0...v9.8.1

v9.8.0

The headline feature is that R3F is now compatible with React 19.3.0. We don't fully support all of the new APIs, but it will not longer conflict to run the latest and greatest React.

In addition we fixed some long standing bugs:

• React roots are configured synchronously and then gated on the renderer if it need async, for example with WebGPURenderer. This means that you won't get awkward out of sync issues.
• Strict Mode no longer causes problems for our canvas. This was related to the async support added a while ago as well.

Have fun!

What's Changed

• fix: corrected broken links by @​dor-rondel in pmndrs/react-three-fiber#3872
• feat: support React 19.3 by @​cades in pmndrs/react-three-fiber#3916
• fix(core): don't tear down a root remounted during the unmount grace period by @​abernier in pmndrs/react-three-fiber#3869
• feat(core): configure and render roots synchronously by @​krispya in pmndrs/react-three-fiber#3925

New Contributors

• @​dor-rondel made their first contribution in pmndrs/react-three-fiber#3872
• @​cades made their first contribution in pmndrs/react-three-fiber#3916

Full Changelog: pmndrs/react-three-fiber@v9.7.0...v9.8.0

v9.7.0

The headline updates for this release are the reconciler fixes. We did a pass to harden what is there against react-dom as the standard.

• R3F's internal children were not being reordered correctly. Basically, if React reordered children, our internal map would drift out of sync and this would cause subtle bugs. This is now fixed. Thanks to @​kvvasuu who reported it and @​wanxiankai who offered a solution.
• Pierced props now reset properly. We had a bug where if a pierce prop was unset, the reconciler would try to reset it to a default value. However, it would set it to the base object instead of the pierced prop. This is fixed now.

// Initial render
<mesh position-x={5} />
// Later render: prop removed
<mesh />
</tr></table>

... (truncated)

Commits

• 53ec672 RELEASING: Releasing 1 package(s)
• e0e9c2d fix(core): bridge Activity visibility into Canvas scenes (#3946)
• 138bfb0 fix(core): stop Canvas rerenders from resetting runtime settings (#3945)
• 2bcc153 fix(web): keep a Canvas root alive while <Activity> hides it (#3943)
• 8965ba4 fix(core): preserve visibility across Activity and Suspense hiding (#3944)
• 9ac7562 fix(core): dispose the renderer R3F creates when its root unmounts (#3942)
• 7db6056 RELEASING: Releasing 1 package(s)
• bc240cc feat(core): configure and render roots synchronously (#3925)
• f0f1cdf fix(core): don't tear down a root remounted during the unmount grace period (...
• 4ae2f81 feat: support React 19.3 (#3916)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by krispyaa, a new releaser for @​react-three/fiber since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 07b6961

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR