Unable to use it on a Cloudflare Worker - eval() statements disallowed

[pseudomrando]

The initialization works on a webpage environment using:
initializeImageMagick(wasmUrl)

However this doesn't work on a Cloudflare worker (either by giving an Url or serving the wasm file itself), I get the following error :

EvalError: Code generation from strings disallowed for this context

Possibly because the initialization uses eval() statements which are unfortunately disallowed in workers environment. So I have no way of initializing the object before using it.

The package is amazing though for my webpage.

[dlemstra]

What do you mean by "or serving the wasm file itself"? Are you talking about the bytes of the wasm files?

I checked the magick.js file of the native library and this is not doing any of the following with a string:

• Using eval() function
• Using new Function() constructor
• Using setTimeout() or setInterval() with string arguments
• Using dynamic code generation methods like Function.prototype.constructor

Can you get more information about what exactly is being blocked?

[dlemstra]

Maybe this is allowed:

const bytes = read('magick.wasm');
const module = await WebAssembly.compile(bytes);
await initializeImageMagick(module);

[pseudomrando]

In Cloudflare workers (and maybe other workers?) the wasm cannot be read dynamically, so it needs to be "served" separately.
Apparently one can do that using an import like statement:
import WASMFILE from '../node_modules/@imagemagick/magick-wasm/dist/magick.wasm';

But then

const wasm = WASMFILE;
const module = await WebAssembly.compile(wasm);
await initializeImageMagick(module);

returns an error from the WebAssembly.compile(wasm) line:
CompileError: WebAssembly.compile(): Wasm code generation disallowed by embedder

Only thing I could find about this is an old threads here:
cloudflare/workers-sdk#1366

[pseudomrando]

What is strange, is that I can use another package jSquash (https://github.com/jamsinclair/jSquash) using the workaround they suggest for Cloudflare workers:

import decode, { init as initWebpDecode } from '@jsquash/webp/decode';
import WEBP_DEC_WASM from '../node_modules/@jsquash/webp/codec/dec/webp_dec.wasm';
await initWebpDecode(WEBP_DEC_WASM);

And it does work. My worker can decode a webp file. Unfortunately not animated webp, while your package does support decoding animated webp which is the feature I need for my project, but can't get it to work.

[dlemstra]

What happens when you call initializeImageMagick with WASMFILE?

[pseudomrando]

Nothing happens. I'm suspecting I'm either misusing it or the size of the wasm was an issue in my worker environment.

In the meantime, I managed to make it work using the other library I was mentioning (@jsquash) with a new feature for decoding animated webp. So the problem is solved on my end.

Thank you for helping me anyway!