[DennisSmolek]

Eleven examples ported from the react-three-fiber v10 example app (example/src/demos/webgpu). The plan is for the R3F docs to link to these pages instead of the dev app in the fiber repo, which goes back to being a test bed.

All run on @react-three/fiber@10.0.0-alpha.6. Each one was built, opened in Chrome on a real WebGPU adapter with no console errors, and its 1600×840 thumbnail was taken from that run.

Example	Shows
webgpu-basics	TSL color/position nodes, background preset on the Canvas
webgpu-shared-uniforms	useUniform, useUniforms, useNodes
webgpu-raging-sea	Leva → useUniforms → named useNodes
webgpu-fog	scoped uniforms + useLocalNodes installing fogNode / backgroundNode
webgpu-motion-blur	useRenderPipeline with a velocity MRT
webgpu-multi-canvas	four canvases on one device, per-canvas fps, HUD
webgpu-shared-renderer	primary, automatic sharing, share="id", share={false}
webgpu-visibility-events	onFramed / onOccluded / onVisible
use-frame-controls	pause/resume/step a job, stop and step the loop
use-frame-fps	per-job fps limits
use-frame-phases	fixed physics phase, interpolation, a custom camera phase

Repo changes

• .syncpackrc.json: the new examples join the fiber v10 group, which now also pins @react-three/tsl. The drei v11 group (11.0.0-alpha.7) is turned on for the ones that use drei, since drei 10 targets fiber 9.
• pnpm-workspace.yaml: @react-three/tsl@10.0.0-alpha.6 excluded from the release-age gate, like fiber alpha.6.
• Schema: @react-three/tsl added as a library (labelled "TSL"), plus the fog and frame-loop tags.
• bin/e2e-exceptions.mjs: all eleven are listed. There's no WebGPU adapter in the harness, and the monkey plugin's CheesyCanvas imports the hoisted fiber 9, so it would mount a v9 root around them.
• Listed as new on the website.

Notes

• Two demos from the fiber app were left out on purpose. WebGPUPrimaryOnly and WebGPURendererRelease are regression repros (#3847, #3926) and stay in the fiber repo.
• drei 11 alpha.7's CameraControls logs deprecation warnings for state.gl and numeric useFrame priorities in webgpu-raging-sea and use-frame-controls. Those come from drei, not from the examples.

🤖 Generated with Claude Code