Ty Mick

Here's the new listing on the Open VSX Registry in case you'd like to take a look: https://open-vsx.org/extension/silvenon/mdx

Great question! Visual Studio Code, while built on top of an open source, MIT-licensed [codebase](https://github.com/Microsoft/vscode), is itself a closed-source, [proprietary](https://code.visualstudio.com/license) product, because Microsoft [adds things](https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code) like branding, telemetry/tracking, and a...

Hi, @breyed— Do the following VS Code launch configurations added to documentation in #28815 help at all? ```json { "version": "0.2.0", "configurations": [ { "name": "Next.js: debug server-side", "type": "node-terminal",...

In case it helps, I've submitted [ctf0.macros](https://github.com/ctf0/macros) (a better-maintained fork of this project) to Open VSX's publishing CI (open-vsx/publish-extensions#198, ctf0/macros#8). It'll be published there within a couple of days, but...

FWIW, upgrading `meow` to at least v6.0.0 should also fix the warning, in case any earlier major versions are easier to upgrade to. v6.0.0 changes the `trim-newlines` version range to...

Oh, good point. Last commit in this repo was Feb 2020 as well, and 179 open issues is a lot for a relatively small project... Bummer.

Oops, GitHub never notified me when this issue was opened; sorry I missed this! I'll try and take a deeper look when I've got some free time.

Another data point in case it helps: When trying to install Node.js v22.11.0 with NVM v1.2.2, `nvm install 22.11.0` silently failed as described, but surprisingly, `nvm install 22.11` worked.

No, this issue still exists. I've continued to use NVM 1.1.12 to avoid it.