wasi-vfs does not seem to work with js profile

[AlawysDelta]

See https://github.com/AlawysDelta/ruby-wasm-test for how to reproduce the issue.

[kateinoigakukun]

Thank you for reporting! Which version of wasi-vfs are you using? Could you check that you are using the same version of wasi-vfs which ruby.wasm links?

ruby.wasm/lib/ruby_wasm/build_system/product/wasi_vfs.rb

Line 5 in 394841d

WASI_VFS_VERSION = "0.1.1"

[Maaarcocr]

Thank you for reporting! Which version of wasi-vfs are you using? Could you check that you are using the same version of wasi-vfs which ruby.wasm links?

ruby.wasm/lib/ruby_wasm/build_system/product/wasi_vfs.rb

Line 5 in 394841d

WASI_VFS_VERSION = "0.1.1"

for the CLI?

[kateinoigakukun]

@Maaarcocr Right, ruby.wasm links libwasi_vfs.a and the CLI version should match with the library version.

[AlawysDelta]

Thank you for reporting! Which version of wasi-vfs are you using? Could you check that you are using the same version of wasi-vfs which ruby.wasm links?

ruby.wasm/lib/ruby_wasm/build_system/product/wasi_vfs.rb

Line 5 in 394841d

WASI_VFS_VERSION = "0.1.1"

We were using wasi-vfs 0.4.0, falling back to 0.1.1 and reintroducing the original browser.umd.js file fixes it, thanks for your help!
It was probably that _inizialize() missing call that broke it.

[kateinoigakukun]

Yes, that's a wasi-vfs's issue, I'll fix it in wasi-vfs

[kateinoigakukun]

The latest wasi-vfs fixed this issue! https://github.com/kateinoigakukun/wasi-vfs/releases/tag/v0.5.0