Unable to Set Local .wasm File in Latest Version

[vsarangan]

Summary:
In version 0.3.1, DotLottieWC allowed setting a custom WebAssembly file via the setWasmUrl export. In the latest version, this functionality is no longer available or documented, breaking local WASM usage and it is taking from cdn.

Steps to Reproduce:

• In version 0.3.1, we were able to set the .wasm file locally as shown:

import { setWasmUrl } from './dotlottie-wc.js';
setWasmUrl('./js/dotlottie/dotlottie-player.wasm');

• After upgrading to the latest version (e.g., @lottiefiles/dotlottie-wc@latest), the setWasmUrl export is missing:
  Latest version does NOT include setWasmUrl
  export { a as DotLottieWC } from './chunk-F5EFWER6.js';

Expected Behavior:
The setWasmUrl API should be retained or replaced with an alternative documented method to allow loading .wasm from a local path, especially for environments where CDN usage is restricted.

[theashraf]

@vsarangan Just to clarify, the setWasmUrl function hasn’t been removed. It’s still available in the latest version. You can see it here in the source:
https://github.com/LottieFiles/dotlottie-web/blob/main/packages/wc/src/index.ts#L6

If you're not seeing it in your project, it might be due to how the package is being imported or bundled. Could you share a minimal reproduction (e.g. via CodeSandbox or a repo) so i can take a closer look ?

[vsarangan]

I'm not using dotlottie-web; the issue is occurring specifically with dotlottie-wc.
Will create the sample and share shortly

[vsarangan]

@theashraf Attached the required file — please refer to the attachment for details - https://limewire.com/d/xMMLX#GSxiC8dAcU