-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nsjail Versus wasm #3670
Comments
Hi @gedw99, I'd like to know more about that. We are using nsjail for running imagemagick and nodejs scripts. For imagemagick, there is a wasm port (https://github.com/dlemstra/magick-wasm), but it didn't support reading PDF (dlemstra/magick-wasm#51), which is mandatory for us. Same for SVG: dlemstra/magick-wasm#19. Do you have another way to suggest? For nodejs scripts, do you have any resource or link on how to compile JS to wasm? |
apologies for random thoughts but https://github.com/ncruces/dcraw https://github.com/jerbob92/go-pdfium-wasm might be cookie crumbs to find folks in similar situations about images and pdf support for their tools. in most cases there are ports to do. I don't have insight into compiling JS to wasm, but someone else may |
Will chime here … sometimes it’s useful to step back and see the best path forward .. Image transforms can be done in pure go compiled to wasm. Sure you might loose some speed but it’s really clean. There are plenty of golang packages that pretty much do what image magic does. pdf. As @codefromthecrypt suggested. It works great. Wazero is so simple to use and there are sone great golang systems built on top to make it very easy . capsule is one on GitHub .. |
Wazero is a no cgo wasm runner and could replace nsjail
The text was updated successfully, but these errors were encountered: