William Boman

Thanks. The problem is that Neovim detects you're using a unix shell (bash) and then assumes that any file inside a directory in `PATH` is executable if there's a match....

Thanks! Would you be able to try out https://github.com/mason-org/mason.nvim/pull/1991 (branch `fix/windows-exepath-unix-shell`) and see if that fixes it (you don't have to manually `:set shell=powershell`)?

I'm afraid this will need more holistic changes. `mason-lspconfig.nvim` v2 now builds on top of the new LSP configuration mechanism introduced in Neovim 0.11. LazyVim seems to use the "legacy"...

Or actually, I now recall spending some time investigating this when it was added. The current behavior mimics the way the VSCode extension works, [with the bundled packages being prioritized](https://github.com/angular/vscode-ng-language-service/blob/8adc17a191acd13a3a2706911a62d658891f5175/client/src/client.ts#L521-L531)....

Thanks! As of v2 the config override for angularls is no longer provided in this repository

Thanks! Server mappings are no longer included in this plugin but instead hosted by the core registry Fixed in https://github.com/mason-org/mason-registry/commit/e30d442091cbb91e99c2427c9f7d6bca95e3ce52

Thanks! Server mappings are no longer included in this plugin but instead hosted by the core registry. Fixed in https://github.com/mason-org/mason-registry/commit/2b1da1b5008d2882aab40cc3221b82d2dfc833b5

I believe this will cause implementations that respect the following rule in the [PURL-TYPES](https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#huggingface) spec to fail: > The version is the model revision Git commit hash. It is case...

FWIW this breaks the test case in an implementation I wrote. I'm not implying that my implementation is correct (it's merely my interpretation of this particular part of the spec)....

Apologies for breaking stuff, was not the intention. It is a major release with breaking changes after all. It's perfectly fine pinning the version to v1 of both plugins!