three-stdlib VS drei

We have forked parts of the three core stuff to minimise breaks. drei for instance uses https://github.com/pmndrs/three-stdlib not examples/jsm. The threejs version you install can still pull the rug but pmndrs works against that with conditionals, shaders for instance are made to function despite three breaking stuff. You can generally rely on it and Fiber + eco system has semantic versioning.

React Three Fiber has been a fantastic way to quickly prototype 3D apps and games, and even efficient enough to carry them through to production. The problem? It’s can be a lot of setup. Just from that last paragraph, you see the string of dependencies R3F uses, and it gets even more complicated from there when you familiarize yourself with the current ThreeJS ecosystem (see: three-stdlib).

three doesn't play well with node and node based environments. poimandres has been building out three's reach more and more, for instance https://github.com/pmndrs/three-stdlib this will all run under next/nuxt or whatever without workarounds.

three is harder to use in next because it doesn't run under node. with three-fiber we have begun to fork some parts of it: https://github.com/pmndrs/three-stdlib that will make it easier to use it under next, even if you use "vanilla" three, stdlib's GLTFLoader will run fine whereas there/jsm won't (without workarounds). is there any reason why you would not want to use react for three though? you're using it for the dom already, r3f is the exact same thing as react-dom, a renderer, it doesn't wrap three.

Same, the pmndrs folks at least pulled some of the examples stuff into https://github.com/pmndrs/three-stdlib which is ESM

you can use the same tools that react users use because we face the same problems. for instance, next/nuxt are running under node, which doesn't understand what "import" means, so you'll not be able to use anything from three/examples/jsm/ (loaders, controls, etc). but we have made solutions for that. for instance https://github.com/pmndrs/three-stdlib generally there is lots on the poimandres github org that is equally valid for vanilla, react, vue and anything else.

don't mix three and react. take an hour to read through react-three-fiber docs and port it. you will be so much better off, 95% of that code will just vanish. poimandres also takes care of all the other parts, for instance three/examples/jsm/* is not node compatible, you can't easily use it in next. but there exists three-stdlib now and many other things that make your life easier.

I have been using react-three-fiber and react-three-drei - the react version of this project. The examples are over whelming and wonderful

https://docs.pmnd.rs/react-three-fiber/getting-started/examp...

One of my favorites is the image gallery. I modified this so that clicking on an image take you into another room (gallery).

https://github.com/pmndrs/drei is a collection of examples and helpers.

Most impressive to me is the one using a GLTF model, video textures on text, reflections and more. A standalone version is

https://bfplr.csb.app/

But even more impressive is the sandbox showing the not-very-many-lines-of-code at

https://codesandbox.io/p/sandbox/ground-reflections-and-vide...

A lot to putting a layer on top of threejs and I have run a fair number of head scratchers. But still the potential is huge. Using threejs has completely changed the way I look at website development. So if you are a svelte person I would definitely look into this.

the shader is here if you want it in vanilla https://github.com/pmndrs/drei/blob/master/src/core/Outlines.tsx though keep in mind it needs some additional work to support skeletons and instances, that's the code in the layout effect.

the eco system gives you so much freedom, especially when it comes to properly align, display your models, and to make them look nice. there are dozens of components for staging, lighting, soft shadows, you would miss out on all of that https://github.com/pmndrs/drei

there are more pain points than can be enumerated. i think you should take a look here https://github.com/pmndrs/drei and pmndrs in general. also the eco system it has covered so far.

there's a whole eco system around three in react and next. it starts with react-three-fiber, drei has tons of helpers, and then there's three-next for when you need 100% lighthouse, persisting canvas across routes etc.

Definitely ThreeJS and specifically React Three Fiber. React Three Fiber is an amazing wrapper around three that greatly reduces boilerplate. And because of how modular react is, the community has grown massively. With lots of helper components in the Drei library, and amazing examples in the author's Twitter. The Codesandbox is also a goldmine of example. And one of the best-produced courses by Bruno Simon to help you get started. He is the creator of this famous portfolio site.

I picked the stack I did to expand upon my skill set. In particular, I wanted to brush up on react-three-fiber, react-spring & drei.

what's the advantage of your version over this one by the developer who created react-three/fiber? https://github.com/pmndrs/drei/blob/master/src/core/OrbitControls.tsx I use the above by importing react-three/drei and it then works just like the one in your example