Environment:
- Next.js application
@splinetool/runtime 1.12.98- Code Export URL:
https://prod.spline.design/OOvyZ3e4WYdxQqxo/scene.splinecode
Problem:
The exported .splinecode is newer than @splinetool/runtime 1.12.98.
The runtime 1.12.98 loads/builds successfully, but the Spline canvas renders 0% opaque and the application fallback activates.
After republishing the exact same Spline scene, the CDN version changed, proving the updated export reached the live Code Export URL.
The previous shader compilation failure was separately fixed in the Spline scene's Sky Backdrop material. After republishing, the shader error disappeared completely.
However, the Spline canvas still paints zero opaque pixels.
Spline's own runtime reports:
"Your .splinecode file is more recent than the library. Please upgrade @splinetool/runtime to the latest version."
Runtime investigation:
1.12.98: builds successfully but cannot render this newer export.1.12.99: does not exist.2.0.1: installs, but the published package is missing required DRACO decoder/WASM files. Next.js/Webpack fails resolving:
../libs/draco/draco_wasm_wrapper.js../libs/draco/draco_decoder.js../libs/draco/gltf/draco_wasm_wrapper.js
2.0.14: installation fails because its dependency tree requires @splinetool/animation-core, which is unavailable from the public npm registry.- Inspection of multiple published 2.x tarballs (2.0.1, 2.0.5, 2.0.9, 2.0.13, 2.0.14) indicates the DRACO packaging problem is present throughout the checked 2.x releases — none of them ship a
libs/draco/ directory or the referenced .wasm/decoder files anywhere in the published tarball.
wasmPath exists as a runtime option, but it cannot solve the 2.0.1 problem because the missing-module failure occurs during bundler/module resolution before the runtime constructor executes.
Ask Spline:
- Which
@splinetool/runtime version is officially compatible with the current .splinecode export format?
- Is there a currently supported runtime release that can load this export in a Next.js/Webpack application?
- If 2.x is the intended runtime, when will the missing DRACO/WASM package files be corrected?
- Is there an officially supported installation/configuration for the current export format?
- Is the "file is more recent than the library" warning expected when using 1.12.98 with current Spline exports?
Environment:
@splinetool/runtime1.12.98https://prod.spline.design/OOvyZ3e4WYdxQqxo/scene.splinecodeProblem:
The exported
.splinecodeis newer than@splinetool/runtime1.12.98.The runtime 1.12.98 loads/builds successfully, but the Spline canvas renders 0% opaque and the application fallback activates.
After republishing the exact same Spline scene, the CDN version changed, proving the updated export reached the live Code Export URL.
The previous shader compilation failure was separately fixed in the Spline scene's Sky Backdrop material. After republishing, the shader error disappeared completely.
However, the Spline canvas still paints zero opaque pixels.
Spline's own runtime reports:
Runtime investigation:
1.12.98: builds successfully but cannot render this newer export.1.12.99: does not exist.2.0.1: installs, but the published package is missing required DRACO decoder/WASM files. Next.js/Webpack fails resolving:../libs/draco/draco_wasm_wrapper.js../libs/draco/draco_decoder.js../libs/draco/gltf/draco_wasm_wrapper.js2.0.14: installation fails because its dependency tree requires@splinetool/animation-core, which is unavailable from the public npm registry.libs/draco/directory or the referenced.wasm/decoder files anywhere in the published tarball.wasmPathexists as a runtime option, but it cannot solve the 2.0.1 problem because the missing-module failure occurs during bundler/module resolution before the runtime constructor executes.Ask Spline:
@splinetool/runtimeversion is officially compatible with the current.splinecodeexport format?