Auto-generated — not yet edited · only the numbers are verified
- TESIGN / RADAR
- REPOSITORY CARD
- pmndrs/react-three-fiber
pmndrs/react-three-fiber
🇨🇭 A React renderer for Three.js
RANKS All-time #225
AT A GLANCE
- LANGUAGE
- TypeScript
- LICENSE
- MIT
- USAGE
- Use, change and redistribute, commercially too. Keep the notice.
- ACTIVITY
- last commit 3 days ago ()
- TOPICS
- 3d
- animation
- fiber
- react
- renderer
- threejs
- HOMEPAGE
- https://docs.pmnd.rs/react-three-fiber
- REPOSITORY
- GitHub ↗
A summary, not legal advice.
README EXCERPT
@react-three/fiber react-three-fiber is a React renderer for threejs. Build your scene declaratively with re-usable, self-contained components that react to state, are readily interactive and can participate in React's ecosystem. [!WARNING] Three-fiber is a React renderer, it must pair with a major version of React, just like react-dom, react-native, etc. @react-three/fiber@8 pairs with react@18, @react-three/fiber@9 pairs with react@19. --- Does it have limitations? None. Everything that works in Threejs will work here without exception. Is it slower than plain Threejs? No. There is no overhead. Components render outside of React. It outperforms Threejs in scale due to React's scheduling abilities. Can it keep up with frequent feature updates to Threejs? Yes. It merely expresses Threejs in JSX, dynamically turns into new THREE.Mesh() . If a new Threejs version adds, removes or changes features, it will be available to you instantly without depending on updates to this library. What does it look like? Let's make a re-usable component that has its own state, reacts to user-input and participates in the render-loop. ( live demo ). Show TypeScript example Live demo: https://codesandbo…
The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.
TIMELINE
- Repository created
- FIRST SEEN BY TESIGN ◌ BACK CATALOG
- Last push
AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →
If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.