rive-app / rive-app/rive-react

Unexpected change of WASM file name causing runtime errors

Open
#340 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.2k
Forks
58
Avg merge
3h 23m
Merged PRs (30d)
6

Description

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/webgl2@2.26.5/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/webgl2@2.26.6/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!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing how the @rive-app/webgl2 packages for versions 2.26.5 and 2.26.6 load their WASM files, focusing on the transition from rive_fallback.wasm to rive.wasm. No repository file or test is named in the issue. Done means confirming whether the rename was intentional and recording the change in the relevant changelog or release notes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, wasm
Domain
frontend, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.