Unexpected change of WASM file name causing runtime errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript, wasm
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.
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/[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.
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!
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 58
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rive-app/rive-react
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
rive-app/rive-react#410 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
rive-app/rive-react#409 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
rive-app/rive-react#400 ·
-
triage
Difficulty 3/5 1-2 days Newbie friendliness 45/100
rive-app/rive-react#392 ·
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 55/100
rive-app/rive-react#386 · 1 reaction ·
All issues in rive-app/rive-react
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
agilepathway/label-checker#710 · 2 comments ·
Maintainers usually reply within 1 day