Skip to content

Unexpected change of WASM file name causing runtime errors #340

@hyuhyuhuhyu

Description

@hyuhyuhuhyu

Hi,

I recently encountered an issue with Rive's WebGL2 WASM file while upgrading from version 2.26.5 to 2.26.6. In version 2.26.5, the library attempted to load the WASM file from the following path:

https://cdn.jsdelivr.net/npm/@rive-app/[email protected]/rive_fallback.wasm

However, after upgrading to 2.26.6, the WASM file name seems to have changed to:

https://cdn.jsdelivr.net/npm/@rive-app/[email protected]/rive.wasm

I couldn't find any mention of this important file name change in the changelog or the official documentation. This unexpected change resulted in runtime errors in our production environment, as the application was still referencing the old file name.

Image

Could you please confirm if this file name change was intentional? Also, it would be great if such important changes could be clearly communicated in future changelogs or release notes to prevent disruptions.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions