runtime: IDBFS is Not defined

Is there an existing issue for this?

I have searched the existing issues

Describe the bug

i’ve been use IDBFS File system module to use sqlite in blazor wasm .net 7 preview 7 but IDBFS is not defined in release mode. also i’ve add : <EmccExtraLDFlags>-lidbfs.js</EmccExtraLDFlags> to my .csproject file

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (10 by maintainers)

Most upvoted comments

@lewing sorry but it’s available in .net 6 and have breaking changes in .net 7. this not better to solve this in .net 7? I think this not a bug or new feature this is changed in .net 7 but I don’t know how to use it in .net 7 and i dont find any documentation about this

@sajjadarashhh we plan to investigate this and fix it if possible. Marking the issue for net8.0 does not mean we won’t fix it in net7.0. Once we have a fix it will be considered for net7.0 but specific emscripten features are not a part of the supported api.

lewing on Aug 30, 2022

The Net7 runtime is not spilling the emscripten guts into JS global namespace anymore. In your code https://github.com/sajjadarashhh/Test.net7/blob/f8280d225d1f4e549c129fc94cfa8b101ce9763a/MultipleEventHandlers/MultipleEventHandlers/wwwroot/file.js#L3-L4

The IDBFS is not global anymore. Please try to replace it with window.Module.FS.filesystems.IDBFS

Please re-open, if that doesn’t help.

pavelsavara on Aug 30, 2022

With wasm-tools workload installed, and using <WasmBuildNative>true</WasmBuildNative>, I can reproduce the issue. @pavelsavara does IDBFS need to be exported in our API?

radical on Aug 29, 2022