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

[young-energy]

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?

[young-energy]

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

[young-energy]

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?

[young-energy]

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!

[kshepherd2013]

Has anyone solved this yet? I am getting the same problem - wasm works in browser environment loaded by url, but not in cloudflare worker environment under any circumstances, e.g.:
import magickWasm from '@imagemagick/magick-wasm/magick.wasm';
...
console.log(magickWasm); // shows it to be an object of type Webassembly.Module
// also (magickWasm instanceof WebAssembly.Module) gives true

This fails:
initializeImageMagick(magickWasm).then(()=>{},(reason)=>{/* .href undefined */});

This fails:
WebAssembly.compile(magickwasm);
// reason for failure: Wasm code generation disallowed by embedder

Any suggestions, please?

[dlemstra]

Have you tried adding a resource what is suggested in their documentation here: https://blog.cloudflare.com/webassembly-on-cloudflare-workers/#how-to-use-webassembly-with-cloudflare-workers?

And then try initializeImageMagick(YOUR_VARIABLE_NAME)?

[dlemstra]

There is no debug version of that method. Should you not get a stacktrace when you don't add the catch in the then? And the exception that is thrown looks like a security error from cloudflare.

[kshepherd2013]

No - no stacktrace if I do not add the catch.
I have no doubt this is a security error thrown by cloudflare.
Cloudflare Worker ecosystem is very buggy, poorly documented, unreliable and unstable.
A stacktrace would tell us which function it cannot handle, and perhaps then let us avoid it.

[kshepherd2013]

To be clear - this bug is in cloudflare code, not this wasm. However there is no chance to get them to help, so any fix would have to be here.
Like other developers above, I have switched to using @jsquash until there is a fix for this.
@jsquash does basic format conversions and resize. For more complicated image manipulation I have been able to use svg2png-wasm
which manipulates images within svg, and also works on Cloudflare Workers.

[dlemstra]

If this is a bug in cloudfare code I then have no idea how to fix that because I cannot debug this. Someone else will need to figure this out and tell me what I can do to work around this issue.

[dlemstra]

Can you give it a try with the latest release @kshepherd2013? I made some changes to the native build as suggested in #203 and I wonder if this now also resolves your cloudflare issue.