@CoenraadS,
As you suggested, vscode.workspace.fs works fine in all the areas of the source code as an alternative of Node fs, but there is just one persistent problem with loading the wasm file.
As you can see, both Node fs and vscode.workspace.fs prints the buffer, but in different length and different encoding. So, there comes the error as you see in the screenshot.
@CoenraadS, As you suggested,
vscode.workspace.fsworks fine in all the areas of the source code as an alternative of Nodefs, but there is just one persistent problem with loading the wasm file.As you can see, both Node
fsandvscode.workspace.fsprints the buffer, but in different length and different encoding. So, there comes the error as you see in the screenshot.Any ideas what can we do about it?