fix(deps): update dependency @react-three/drei to v10 by SamuelIVX · Pull Request #11 · SamuelIVX/SamuelIVX.github.io

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: personal_website@0.0.0
npm error Found: @react-three/fiber@8.18.0
npm error node_modules/@react-three/fiber
npm error   @react-three/fiber@"^8.17.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @react-three/fiber@"^9.0.0" from @react-three/drei@10.7.7
npm error node_modules/@react-three/drei
npm error   @react-three/drei@"^10.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-01-29T23_07_00_103Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-01-29T23_07_00_103Z-debug-0.log

coderabbitai · 2026-01-29T09:25:09Z

📝 Walkthrough

Walkthrough

Updated @react-three/drei dependency from ^9.121.2 to ^10.0.0 in package.json. No other files, scripts, or application code were modified.

Changes

Cohort / File(s)	Summary
Dependency Updates `package.json`	Bumped `@react-three/drei` dependency from `^9.121.2` to `^10.0.0` (major version update).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I hopped a patch and found a view,
Ten now glints where nine once grew,
Ears perked up for bundled cheer,
A tiny leap into the new,
Wiggle, whisker—code revue!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: updating the `@react-three/drei` dependency to v10. It uses a conventional commit format (fix type with deps scope) and clearly conveys the primary purpose of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch renovate/react-three-drei-10.x

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Around line 16-18: The dependency mismatch between `@react-three/drei` (v10) and
`@react-three/fiber` (v8) must be resolved; either upgrade React to 19 and bump
`@react-three/fiber` to ^9.0.0 and then update `@react-three/drei` to ^10.0.0
(verify app compatibility and run tests), or revert `@react-three/drei` to a v9
release that supports `@react-three/fiber`@^8 (change "@react-three/drei" to a
^9.x version in package.json), run package install, and validate the app; choose
the revert-to-v9 path if you cannot migrate to React 19 now.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 659491b and e8e44db.

📒 Files selected for processing (1)

package.json

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

coderabbitai · 2026-01-29T09:28:44Z

package.json

    "@emailjs/browser": "^4.4.1",
-    "@react-three/drei": "^9.121.2",
+    "@react-three/drei": "^10.0.0",
    "@react-three/fiber": "^8.17.12",


⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Query npm registry for peerDependencies echo "=== `@react-three/drei`@10.0.0 peerDependencies ===" npm view `@react-three/drei`@10.0.0 peerDependencies --json 2>/dev/null || echo "Failed to query" echo -e "\n=== `@react-three/fiber`@9.0.0 peerDependencies ===" npm view `@react-three/fiber`@9.0.0 peerDependencies --json 2>/dev/null || echo "Failed to query" echo -e "\n=== `@react-three/fiber`@8.17.12 peerDependencies ===" npm view `@react-three/fiber`@8.17.12 peerDependencies --json 2>/dev/null || echo "Failed to query"

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 729

🏁 Script executed:

#!/bin/bash # Check if package.json exists in repo and what React version is pinned if [ -f "package.json" ]; then echo "=== React version in project ===" rg '"react":\s*' package.json -A 0 echo "" echo "=== Full dependencies section ===" cat package.json | head -50 fi

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 1433

🌐 Web query:

@react-three/drei 10.0.0 peerDependencies @react-three/fiber requirements

💡 Result:

@react-three/drei@10.x declares a peer dependency on @react-three/fiber ^9.0.0 (example: @react-three/drei@10.0.3’s package.json). [1]

Also, I couldn’t find a stable @react-three/drei@10.0.0 published on npm—only 10.0.0-rc.* and then 10.0.1+. [2]

Sources:
[1] UNPKG @react-three/drei@10.0.3 package.json (peerDependencies) https://app.unpkg.com/@react-three/drei@10.0.3/files/package.json
[2] npm versions/tags showing 10.0.0-rc.* and 10.x latest https://www.npmjs.com/package/@react-three/drei?activeTab=versions

🌐 Web query:

@react-three/fiber 9.0.0 peerDependencies React version requirements

💡 Result:

For @react-three/fiber v9.x (including 9.0.0), the package’s peer dependency requirement for React is React 19:

react: ^19.0.0

react-dom: ^19.0.0 (peer, marked optional in peerDependenciesMeta) [1][2]

Sources: the v9 peer dependency set is shown in the published package metadata for 9.3.0 [1] and 9.2.0 [2].

Resolve the @react-three/drei v10 peer dependency mismatch with @react-three/fiber v8.

@react-three/drei@10.x requires @react-three/fiber@^9.0.0, but the project pins @react-three/fiber@^8.17.12. However, @react-three/fiber@9.x requires React 19, while the project is on React 18.3.1. This creates an unresolvable conflict.

You have two options:

Option A (full upgrade): Upgrade React and fiber together:

"react": "^18.3.1", - "react-dom": "^18.3.1", + "react-dom": "^19.0.0", "@react-three/fiber": "^8.17.12", + "react": "^19.0.0",

(Verify application compatibility with React 19.)

Option B (revert drei): Keep drei on v9 until React 19 migration is ready:

- "@react-three/drei": "^10.0.0", + "@react-three/drei": "^9.121.2", "@react-three/fiber": "^8.17.12",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

"@emailjs/browser": "^4.4.1",

"@react-three/drei": "^9.121.2",

"@react-three/drei": "^10.0.0",

"@react-three/fiber": "^8.17.12",

"@emailjs/browser": "^4.4.1",

"@react-three/drei": "^9.121.2",

"@react-three/fiber": "^8.17.12",

🤖 Prompt for AI Agents

In `@package.json` around lines 16 - 18, The dependency mismatch between `@react-three/drei` (v10) and `@react-three/fiber` (v8) must be resolved; either upgrade React to 19 and bump `@react-three/fiber` to ^9.0.0 and then update `@react-three/drei` to ^10.0.0 (verify app compatibility and run tests), or revert `@react-three/drei` to a v9 release that supports `@react-three/fiber`@^8 (change "@react-three/drei" to a ^9.x version in package.json), run package install, and validate the app; choose the revert-to-v9 path if you cannot migrate to React 19 now.

SamuelIVX · 2026-02-06T02:55:16Z

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

SamuelIVX added the dependencies label Jan 29, 2026

coderabbitai bot reviewed Jan 29, 2026

View reviewed changes

fix(deps): update dependency @react-three/drei to v10

bacb425

SamuelIVX force-pushed the renovate/react-three-drei-10.x branch from e8e44db to bacb425 Compare January 29, 2026 23:07

SamuelIVX closed this Feb 6, 2026

SamuelIVX deleted the renovate/react-three-drei-10.x branch February 6, 2026 02:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency @react-three/drei to v10#11

fix(deps): update dependency @react-three/drei to v10#11
SamuelIVX wants to merge 1 commit intomainfrom
renovate/react-three-drei-10.x

SamuelIVX commented Jan 29, 2026 •

edited

Loading

Uh oh!

SamuelIVX commented Jan 29, 2026 •

edited

Loading

Uh oh!

coderabbitai bot commented Jan 29, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Jan 29, 2026

Uh oh!

SamuelIVX commented Feb 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

SamuelIVX commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Configuration

Uh oh!

SamuelIVX commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: package-lock.json

Uh oh!

coderabbitai bot commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

SamuelIVX commented Feb 6, 2026

Renovate Ignore Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

SamuelIVX commented Jan 29, 2026 •

edited

Loading

SamuelIVX commented Jan 29, 2026 •

edited

Loading

coderabbitai bot commented Jan 29, 2026 •

edited

Loading