Skip to content

WASM fallback behavior configuration #403

@Lighttree

Description

@Lighttree

Hello,

I've recently started to use Rive and observed wasm fallback behavior:

const backupJsdelivrUrl = `https://cdn.jsdelivr.net/npm/${packageData.name}@${packageData.version}/rive_fallback.wasm`;

While I understand why this might be useful and bulletproof, it is also a security risk because your application will download a resource from a third-party CDN without any integrity or control over it. As far as I can see, there is no option to disable or configure this fallback.

Perhaps you could consider adding such an option? Either disable it or provide a fallback URL the same way as it is done for the "first party" wasm URL.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions