You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(PYLANCE/C++/...) Patch Microsoft extensions not working on VSCode Forks (VSCodium / Cursor / etc.)
Patcher for Microsoft Extensions
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!
Microsoft claims Visual Studio Code (VS Code) is open source, yet it restricts the use of its Marketplace extensions in non-Microsoft products like VSCodium (telemetry/tracking free open source fork), Cursor, Windsurf, Trae, and other VS Code-based IDEs, enforcing what some see as monopolistic control. This guide provides a workaround to enable the VS Code Marketplace in VSCodium and Trae (more to be added soon), allowing you to freely use extensions. Note that using the VS Code Marketplace with non-Microsoft products may violate its terms of use, which state that extensions are intended for use only with Microsoft Visual Studio products. Proceed at your discretion after reviewing the terms.
Enabling VS Code Marketplace in VSCodium
To configure VSCodium to use the VS Code Marketplace instead of the default OpenVSX Registry, you can either set environment variables or create a custom product.json file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Userscript for adding video controls on Instagram in your browser
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.
Python code to get text and link of the bookmarked tweets and save in markdown
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters