This script works for patching any Microsoft VSCode extension so it will work on it's forks including:
- VSCodium
- Cursor
- Windsurf
This discussion motivated me to make this simple script: VSCodium#1641
Currently tested only on Pylance/VSCodium but as long as it's Microsoft's extension that blocks VSCode forks, it should be fine.
The code uses fairly generic patterns to ensure it's cross-compatible with other extensions than the one I tested!
- Find a location of your VSCode fork's extensions directory (example for VSCodium on Linux:
~/.vscode-oss/extensions/) - Select folder that matches ID of the extension you want to patch
- Put the script inside of that folder and run it ONCE
Note
Running it multiple times shouldn't break the extension but adds unnecessary code to it that will never get executed anyways.
A: If they'll patch it, I'll find another way. It was just dumb for them to limit their products in such way. If they don't like when people use other versions of VSCode then they should make their product better, so others won't even think about switching. Instead they make other people's and open-source ecosystem's life more miserable.
Besides, I'm 99% certain it'll work for more time than some solutions mentioned in discussion above since my method doesn't even touch obfuscated variables that might change between updates. (that's the right way of making mods, guys)
A: Please, start by affording some braincells and get OS that won't self-destruct on every update. Then I will help you. Other than that, look at the code of the script and figure it out.
I recommend turning off auto-updates for Pylance for as long as your extension works since you have to patch that file on every update.