When @syrusakbary and I were looking into why the vscode-wasm addon wouldn't load, we discovered that VS Code doesn't allow plugins written in ES Module syntax (https://github.com/microsoft/vscode/issues/130367). It'll work fine while developing, but then when you compile the *.vsix and install it, it'll silently fail to load on startup because VS Code does a require("./path/to/extension") and require() isn't compatible with ES Modules.
This should fix the underlying issue behind https://github.com/wasmerio/vscode-wasm/issues/41.
When @syrusakbary and I were looking into why the
vscode-wasm
addon wouldn't load, we discovered that VS Code doesn't allow plugins written in ES Module syntax (https://github.com/microsoft/vscode/issues/130367). It'll work fine while developing, but then when you compile the*.vsix
and install it, it'll silently fail to load on startup because VS Code does arequire("./path/to/extension")
andrequire()
isn't compatible with ES Modules.CC: https://github.com/wasmerio/wai/pull/13