react-three-next VS node-canvas

ps, you can also try https://github.com/pmndrs/react-three-next where we have abstracted this stuff. it gets 100% lighthouse score for performance, accessibility, best practices and seo.

react-three-next

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.

It’s a good combination, react-three-fiber expresses three in react, react-three-next makes for a good starting template for common issues like persisting canvas between routes. And Vercel is funding both pmndrs and r3f.

The team at r3f are doing killer work. Check out this repo for a way to do SSR with their react renderer. https://github.com/pmndrs/react-three-next

you could also check out https://github.com/pmndrs/react-three-next which is a nextjs starter. it gives you almost 100% lighthouse, and it has all these little tricks inbuilt.

Also check out https://github.com/pmndrs/react-three-next uses react three fiber, which is awesome.

There is a known issue since v2.10.2 ,the registerFont() is not working in windows.

If you're interested in node-compatible canvas implementations, there are several:

* canvaskit-wasm, from the skia project. I don't think it's gpu-accelerated: https://github.com/google/skia/tree/main/modules/canvaskit/n...

* @napi-rs/canvas. This is the fastest binding: https://github.com/Brooooooklyn/canvas?tab=readme-ov-file#pe...

* node-canvas. Uses Cairo instead of Skia: https://github.com/Automattic/node-canvas

Assuming SWR (stale while revalidate) is working, we could definitely use the ability to edit images in workers. We would need support for node canvas or something similar.

So at this point, I have all the images and the data required to align the images. I used node-canvas to do that. So here's how I aligned the images:

ECharts was originally a Baidu project, released under https://github.com/ecomfe/echarts (ecomfe = "E-commerce frontend"?). They still maintain some of the auxiliary libraries.

I've been using it since around ... 2018-ish[0]? ... as a replacement for Google Charts. It was my first time using a big library from one of the Chinese tech giants -- basic docs and tutorials in English, then all the advanced stuff (and comments) written in Chinese. I was impressed by how comprehensive the charts library was, and how they'd obviously invested a lot of brainwork into the configuration system. IMO it's one of the highest-quality data visualization libraries in JavaScript unless you're willing to dive deep into something like d3.js.

The blog post's author describes running echarts in a headless Chrome, though, which seems insane to me. It's JavaScript rendering to a -- can't it run in Node with https://github.com/Automattic/node-canvas ?

[0] A small publicly-accessible example: https://john-millikin.com/reddit-front-page-2018#by-domain

node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.0/canvas-v2.11.0-node-v93-darwin-unknown-arm64.tar.gz

Another approach is it to create a background image and insert the texts and the metadata with a canvas library like node-canvas. This approach is very well described in this Learn With Jason episode. But with a canvas library we have to specify on which coordinates we want to render our texts and it does not wrap automatically if it becomes to long.

Never used it but probably this: https://github.com/Automattic/node-canvas

I found this issue: https://github.com/Automattic/node-canvas/issues/1974 and somebody commented with a link about node buffers. So I decided to test these parts.

Some popular Node.js libraries for manipulating images are node-canvas and sharp.