Clément Roche

I think that's because react-use-measure is based on ResizeObserver which runs its callback a frame after its initialization. One solution would be to call getBoundingClientRect immediately when element is binded.

Are you lazyloading your canvas ? Importing three.js and running WebGL has a huge impact on loading speed, you must wait for your page content to be loaded before to...

The issue was already submited here: https://github.com/pmndrs/react-three-next/issues/124, I provided a fix by using Lenis as scroll provider but i didn't get any news since https://github.com/pmndrs/react-three-next/pull/123.

I've pushed a `syncTouch` prop in v1.0.11, you can try it live on https://lenis.studiofreight.com/. The idea is to mimic native touch scroll while allowing webgl/dom sync

any solution planned @developit ? this might become a real issue once maintainer switch to Next.js app folder see next.js notice https://nextjs.org/docs/getting-started/react-essentials#third-party-packages

Now i realise that the issue comes from rollup itself not directly from microbundle, i'm gonna take a look at the thread you shared, thank you

I tried both solutions @ForsakenHarmony, still have this warning `Module level directives cause errors when bundled, 'use client' was ignored.` pretty sure `rollup.config.js` is ignored by microbundle, right ?

Thank you! Hmmm for the scale question i'm not sure what you have in mind but ideally we should be able to do anything with this texture , this should...

I'm rendering Rive using @rive-app/webgl. Rive is not the issue actually, it works very well. The memory issue come when calling `texSubImage2D` using three.js, especially when canvas is huge (>512px)....

I have nothing to say about rive renderer, both canvas and webgl are 1000x better than lottie. The memory leak comes from `texSubImage2D` i could use any canvas even an...