-
Notifications
You must be signed in to change notification settings - Fork 53
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
Extension fails to start using VSCode Insiders #195
Comments
I experience this under Ubuntu 20.04 as well. Same description in the extension host log when running code-insiders. |
hmm, this seems strange - the extension doesn't use any proposed APIs and has previously worked fine in insiders. Not sure why this is happening now. Will have a look into it. |
I suspect it's probably this issue - microsoft/vscode#111913 - I might be able to just compile with a newer typescript version to work around it |
well, seems like changing the compiler version fixes the issue but breaks a whole load of tests, unfortunately not in a great position to debug this right now and check if they're real failures, so will have to leave it for another day |
@mjcrouch The tests probably break because in newer versions of TypeScript when you do var __importStar = (this && this.__importStar) || function (mod) {
if (mod && mod.__esModule) return mod;
var result = {};
if (mod != null) for (var k in mod) if (Object.hasOwnProperty.call(mod, k)) result[k] = mod[k];
result["default"] = mod;
return result;
};`
const vscode = __importStar(require("vscode")); In other words, module properties will have a getter and no setter. If you try to mock them out using a test framework like Jest, you'll get an error. In Jest, I get:
|
Fixed upstream: microsoft/vscode#112141 |
thanks for the update! |
Describe the bug:
When running out of VSCode Insiders the extension fails to start. Looking at the Extension Host Log:
I have tried adding
"enable-proposed-api": ["mjcrouch.perforce"]
to my argv.json, but the error persists.Expected behavior:
Extension starts and behaves normally
To Reproduce:
Install perforce extension on VSCode insiders.
Versions & Details:
Additional context
It'd be really helpful to use this extension in insiders. Some vscode extension development which I want to source control with Perforce has to use insiders. The extension works as expected in my non-insiders version of VSCode.
The text was updated successfully, but these errors were encountered: