You don't, but it makes it easier to integrate in to some existing code. Usually these libraries are written for personal reasons (eg needing it yourself) and then open sourced. If you're making a React app at the time then it ends up being a React library.
One day I'm going to 'un-React' Neon (see my other comment), but until then it 'needs' it.
I'm working on something vaguely similar but for foreground effects - https://github.com/onion2k/react-neon/ - it's a library that adds a canvas over a component with an interactive effect. It's very early, and Chrome only because it relies on ResizeObserver (but that's going to change to use Mutation Observer very soon).
I added an example that puts Inigo Quilez's WebGL raymarched clouds on a fullscreen canvas yesterday. It makes my iMac sound like a jet engine. https://react-neon.ooer.com/fullscreen/clouds/
8 comments
[ 3.4 ms ] story [ 22.1 ms ] threadLive demo: https://codepen.io/lucagez/full/oQoRyK/
One day I'm going to 'un-React' Neon (see my other comment), but until then it 'needs' it.
I'm working on something vaguely similar but for foreground effects - https://github.com/onion2k/react-neon/ - it's a library that adds a canvas over a component with an interactive effect. It's very early, and Chrome only because it relies on ResizeObserver (but that's going to change to use Mutation Observer very soon).
I added an example that puts Inigo Quilez's WebGL raymarched clouds on a fullscreen canvas yesterday. It makes my iMac sound like a jet engine. https://react-neon.ooer.com/fullscreen/clouds/