From 42fceb5247376c4b86227d457438591e623c58e5 Mon Sep 17 00:00:00 2001 From: Ragulsundaram <41433645+Ragulsundaram@users.noreply.github.com> Date: Thu, 12 Nov 2026 23:56:35 +0530 Subject: [PATCH] r3f: three peer range >= 0.180.0 (HDRLoader first ships in 0.180) src/three/scene.ts imports three/examples/jsm/loaders/HDRLoader.js, added in three 0.180; with three 0.170-0.179, inside the old range, every scene fails to bundle. --- sdk/r3f/package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk/r3f/package.json b/sdk/r3f/package.json index 2fe251ea..1504ab18 100644 --- a/sdk/r3f/package.json +++ b/sdk/r3f/package.json @@ -14,7 +14,7 @@ "//": "In a project, three and @react-three/fiber are its own (raea add three@0.185.0 @react-three/fiber@9.8.2): the bundler resolves them from the project, so a scene and raea share one copy. Here, for the package's tests and tsc, React is the SDK's own (sdk/raea), linked; sdk/playable's bundler resolves three to its own copy, so a playable carries one.", "peerDependencies": { "@react-three/fiber": ">=9.0.0", - "three": ">=0.170.0" + "three": ">=0.180.0" }, "devDependencies": { "@react-three/drei": "10.7.9",