yes, triangulation and glyph paths should be better, but I’d be happy to improve it if you find an edge case. the entire pipeline is optimized for text; triangulation is handled by libtess2, based on the GLU tessellator, which can handle very difficult paths. IIRC three.js uses earcut

extrusion (depth parameter) is possible; is there something about it that is undesirable for your use case compared to the native three.js extrusion?

hi! it produces mesh (three.buffergeometry) only; it uses its own shape representation during tessellation rather than three.shape, I hope this works for you

three-text is now available on npm and github github.com/countertype/...

*Debs! Guess there’s no editing on Bluesky!