canvaskit-wasm rendering backend support.

[StringKe]

Is it possible to support https://www.npmjs.com/package/canvaskit-wasm to render content, so that the effect of support in nodejs will be very good. At the same time canvaskit-wasm is a package of skia, and skia can support svg output

[ivanpopelyshev]

Yes, I know people who used it with pixi. Whats your problem with it?

[StringKe]

I can repackage canvaskit to provide it with svg canvas capabilities. If pixi supports canvaskit, then pixi can be used to output svg directly. At the same time, skia's svg canvas supports direct conversion of text to path. At the same time, the layout of text in skia is very good.

[ivanpopelyshev]

If pixi supports canvaskit, then pixi can be used to output svg directly.

Wait what? Why do you need pixi to make an svg file and not render it?

I mean, why do you need pixi at all if your app doesnt have webgl environment?

[ivanpopelyshev]

Maybe you mean that SVG rendering should be made through canvaskit... However supporting canvaskit means we just .. copy its texture output to our texture :) every frame. Because canvaskit on its own cant share context with anything else.. wait, canvaskit will own the texture output?

[StringKe]

You can check canvaskit's typescript type definition.

https://github.com/google/skia/blob/main/modules/canvaskit/npm_build/types/index.d.ts#L2629
https://skia.org/docs/user/modules/canvaskit/

I don't know if this is what you need

[StringKe]

If pixi supports canvaskit, then pixi can be used to output svg directly.

Wait what? Why do you need pixi to make an svg file and not render it?

I mean, why do you need pixi at all if your app doesnt have webgl environment?

I want to directly use pixi api to render jpg, png, svg and pdf at the same time. The parent project (skia) of canvaskit contains these functions.

[bigtimebuddy]

PixiJS does not yet support rendering with Node.js, but we are working on it and have a plan. Some users have hack this, but it's not something that works out of the box. However, it's on the roadmap for v6.

[StringKe]

I understand that I recommend the pixi.js team to consider using canvaskit-wasm so that both the browser and node can use the same rendering program.

[eXponenta]

Why this is not real:

1. Need support 4 render backends (with providing a equals results ): Canvas2D, Webgl/2, WebGPU (in future) and CanvasKit
2. Node can't to use hybrid render pipelines, some plugins require it. Resource providers will not working, becuase there are not Image, imageBitmap, dom, canvas ... etc - need to full refact of all comunitty libs and introduce a lot of polyfils.
3. Wasm. Canvas kit has huge WASM binary size and glue code. You can't embed runtime to package, same problem how and with basis. If you need use basis - you runtime size increase and 400kb. CanvasKit has runtime bundle greater that 6mb.!!
4. Huge architectural changes.