[Brian Fernandes]

If you’ve observed a sudden loss of functionality offered by an extension in CodeMix, the problem could have been caused by an automatic extension update when using CodeMix and VS Code simultaneously. A few popular extensions, like Vetur, Python and ESLint could be affected.

VS Code and CodeMix share the same set of extensions, and VS Code may occasionally update an extension to a version that requires a higher version of the Code OSS engine that CodeMix integrates. This prevents the extension from working in CodeMix, leading to loss of functionality. Of course, if exclusively used, CodeMix will not automatically update extensions to incompatible versions.

Our team is working on improving this behavior for our next release, here are some workarounds that can be applied right now if you are currently affected.

1) Downgrade to an earlier version of the extension
Uninstall the extension in VS Code / CodeMix and using a VSIX file, install the previous version of the extension.

2) Modify the extension’s requirements
a) Shut down both VS Code and CodeMix.
b) Go to [user_home]/.vscode/extensions and find the folder containing the affected extension.
c) Make a backup of the package.json file and check if the engines.vscode property is greater than 1.20.1. If it is, change the value to 1.20.1. This will allow the extension to work in CodeMix and hopefully most functionality will be restored. Functionality that relies on a later version of the Engine will not work.

In VS Code, you may also want to use the Extensions: Disable Auto Updating Extensions command to prevent updates until this issue is resolved.

[Author]

Posts