Webassembly SuperTux no longer working with 0.7.0

[enderandrew]

SuperTux Version

0.7.0

System Information

Webassembly

Expected Behavior

Supertux runs in the browser

Actual Behavior

The game crashes with no visible error after loading the large data file. I tried both 0.7.0 and the latest nightly build. Both versions of the Webassembly fail with the same error in the Javascript console of:

[FATAL] /home/runner/work/supertux/supertux/src/supertux/main.cpp:833 Unexpected exception: Couldn't initialize physfs: no error
(anonymous) @ supertux/:315
put_char @ supertux2.js:1
write @ supertux2.js:1
write @ supertux2.js:1
doWritev @ supertux2.js:1
_fd_write @ supertux2.js:1
$func12001 @ supertux2.wasm:0x51646f
$func1691 @ supertux2.wasm:0xa4c9f
$func665 @ supertux2.wasm:0x21421
$func11831 @ supertux2.wasm:0x50d08d
$func3414 @ supertux2.wasm:0x19cd14
$func2188 @ supertux2.wasm:0xe9764
invoke_iii @ supertux2.js:1
$func399 @ supertux2.wasm:0xcceb
$func654 @ supertux2.wasm:0x20ef8
invoke_ii @ supertux2.js:1
$ig @ supertux2.wasm:0x231eb3
callMain @ supertux2.js:1
doRun @ supertux2.js:1
(anonymous) @ supertux2.js:1
setTimeout
run @ supertux2.js:1
removeRunDependency @ supertux2.js:1
processPackageData @ supertux2.js:1
await in processPackageData
runWithFS @ supertux2.js:1

Steps To Reproduce Actual Behavior

Attempt to load the latest SuperTux webassembly

Additional Information

No response

Guidelines For Reporting Issues

• I have read https://github.com/SuperTux/supertux/blob/master/CONTRIBUTING.md#bug-reports.
• I have verified this isn't an issue that's already been reported.
• I have verified this isn't a discussion, or an issue about a crash or a feature request, but rather an actual bug ─ that is, the game did something not intended.
• I have verified this issue is not about wrong translations (use Transifex for those), or anything unsupported (e.g. third-party add-ons).
• In this report, I have only included details about one (1) bug.
• If I make a mistake while submitting this report, I agree to use the "Edit" feature to correct it, instead of closing this issue and opening a new one.