npm upgrade
Home@react-three/fiber 6 → 7
6.2.3 → 7.0.29. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@react-three/fiber 7.0.29 changes how many arguments some functions take.
- Removed
- 0
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 2
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @react-three/fiber@6.2.3..7.0.29
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Signature changes
Still exported, but the number of arguments it reads changed.
- createPortal3 → 2 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 11, 2026. @react-three/fiber on lurq.