-
-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can no longer use extensionDependencies because of Proposed API / VS Code 1.54.1 #444
Comments
Same here, error in vscode log (extension host) but sumneko extension still works, but extension (WoW API) depending on sumneko can not initialize if
|
Actually it does not seem related to |
I have no idead. The only place where related functions are used is https://github.com/sumneko/vscode-lua/blob/0ca56305cbe34e03654231be32222eb2824675ac/client/src/languageserver.ts#L150 . However, after I tried to remove it, this error still appeared. |
fixed by LuaLS/vscode-lua@f79d268 |
Describe the bug
My EmmyLua extension no longer works, in the VS marketplace and when trying to debug it.
The error shows your extension is using "Proposed API" but it does not actually use that right?
This bug seems to happen since the VS Code 1.54.0 or 1.54.1 update.
To Reproduce
Steps to reproduce the behavior: (see https://github.com/Ketho/test-sumneko-lua)
Create a new extension with yo code
Add the extension dependency.
F5
. It fails to activate.Environment (please complete the following information):
Additional context
I rolled back VS Code to 1.53.2 and I could successfully debug the test extension again.
Same for my EmmyLua extension (ketho.wow-api 0.3.3 with sumneko.lua 1.17.4)
There seems to be something wrong with VS Code 1.54.0 or 1.54.1 that breaks
extensionDependencies
Proposed API
I also tried to enable Proposed API as described on https://code.visualstudio.com/api/advanced-topics/using-proposed-api
"enableProposedApi": true
to package.json for both the sumneko.lua and test extensions.npx vscode-dts dev
"--enable-proposed-api"
to my launch.json args,But I failed, nothing fixed the error. This is the first time I tried to enable the Proposed API though.
The text was updated successfully, but these errors were encountered: