William McMurray

Ah ! good to know. Sadly I couldn't find a more recent workaround to this issue dating from 2015 :/ And I am unsure of the best approach for this......

It would be simpler yes, and it would be more consistant with the rest of the API which consists of methods instead of boolean values, but that would be a...

@interstates21 Try adding this to your webpack config file : ```js node: { fs: 'empty' } ``` I took that trick from an old project of mine, but I can't...

+1 That `forceClear = true` got me real confused this morning, I didn't expect `Scene.background` to still clear the color even if `autoClear === false` 😕 ! For that reason,...

> Very nice! Is there any case in which we wouldn't want to have this always enabled? Also when a user **want** to display very sharply pixelated transparent texture (low...

Btw (since no one mentioned it), it seems to be possible to make a "classic" skybox that rotates using an array of 6 materials. something like this : ```js const...

Just to add on top of my [previous comment](https://github.com/mrdoob/three.js/issues/16328#issuecomment-736676790), the method proposed will generate **6 draw calls per frame** (1 per material) this is not very good... along with [specificities...

Please explain how does [the documentation](https://socket.io/docs/v4/emitting-events/#volatile-events) fixes (or clarify) this issue ? 🤔 Maybe this part : `Volatile events are events that will not be sent if the underlying connection...

Yes very clear 🙂 but when is it useful to discard events based on "_is the server/client already sending something_" ? 🤔 I can't find any use case for this......

@unframework I also wish your awesome tech was decoupled from React ! 🙋🏼‍♂️ 🙏🏼 In fact, I would have expected it to belong in the exemples considering it has no...