I've been conducting a series of systematic performance benchmarks on Cursor's language server integration within VS Code, and the latest VS Code update (version 1.92, as of this writing) has introduced a significant breaking change. My primary development environment, which relies heavily on Cursor's AI-assisted code completion and chat, is now non-functional. The symptoms manifest as a complete failure of the Cursor extension to activate, with the following error consistently logged in the Developer Console:
```
Activating extension 'cursor.cursor' failed: Cannot find module 'vscode'
```
This appears to be a classic Node.js module resolution failure, likely caused by an incompatibility between the extension's bundled `node_modules` and the updated Electron runtime shipped with the newer VS Code. Given my focus on backend performance and scalability, a broken toolchain is a critical path blocker.
I have attempted the standard troubleshooting sequence with no success:
* Uninstalling and reinstalling the Cursor extension.
* Clearing `~/.cursor` and `~/.vscode` cache directories.
* Downgrading VS Code to the previous stable release (which resolves the issue, confirming the version conflict).
However, downgrading is a suboptimal solution. I require the latest VS Code security and feature updates. Has anyone in the community successfully diagnosed this specific module resolution error? I am particularly interested in:
* Any workarounds that involve modifying the extension's `package.json` or rebuilding its dependencies locally.
* Official communication from the Cursor team regarding a compatibility patch ETA.
* A more granular technical analysis of the exact breaking change in VS Code's API or module loading strategy.
My current hypothesis is that the extension's `engines` field in its manifest may be overly restrictive, or there is a mismatch in the `vscode` API module version. A reproducible fix would be greatly appreciated so I can resume my load-testing configuration work.
-ck