Things work well in local development, but failed in production.

Steps to reproduce:

1. Install wasmoon by npm install wasmoon in a Nextjs 14 project.
2. Create an engine according to its documentation.

1
const { LuaFactory } = require('wasmoon')
2

3
// Initialize a new lua environment factory
4
// You can pass the wasm location as the first argument, useful if you are using wasmoon on a web environment and want to host the file by yourself
5
const factory = new LuaFactory()
6
// Create a standalone lua environment from the factory
7
const lua = await factory.createEngine()

3. Create a route file whether using page or app directory.
4. Using the engine to execute some lua strings in the route handler.
5. Deploy it to Vercel production.
6. Request the api, you will see the error.

Wasmoon uses emscripten to generate the wasm file, and there's a glue.js file to load and Instantiate the wasm module. In Vercel production environment, it couldn't find the wasm file. I tried to provide a http resource of that wasm file(This is supported by wasmoon), its instantiation failed too.

I really appreciated if anyone could help with this.