Rafał Chłodnicki

> If LSP-typescript and LSP-volar use the same base `"selector"`, shouldn't it work if one of them increases the priority for script blocks via `"priority_selector"`? Check my initial comment for...

I think I can manage that by just disabling conflicting capabilities for the vue server as part of enabling "hybrid mode" (which will be done on explicit action and stored...

rename/prepareRename is another functionality that shows the issue with LSP-vue/LSP-typescript running together - https://github.com/sublimelsp/LSP-vue/issues/164 I suppose in that case it would be somewhat reasonable to try every server until non-empty...

BTW. The chain of calls that leads to this code is: `nuxi` (`loadKit`) -> `@nuxt/kit` (`loadNuxt`) -> `pkg-types` (`resolvePackageJSON`) -> `mlly` (`resolvePath`) -> `mlly` (`_resolve`)

Hmm, there is more issues like that elsewhere. For example in `getPackageScopeConfig` which I think comes from internal Node libs. So I think the solution to issues like that is...

This rabbit hole goes deep. The first directory that is involved and that doesn't include the trailing slash is the `rootDir` one resolved in https://github.com/nuxt/nuxt/blob/184d57bb1923b8bf21a372eabdb67e1241d2023f/packages/nuxi/src/commands/dev.ts#L41. Forcing trailing slash here fixes...

> I think first good step would be making a minimal mlly reproduction to test the behavior if you can help 🙏🏼 I'm thinking that a unittest for that would...

> But in general, if the use case is only the interaction between LSP-volar and LSP-typescript, shouldn't this whole logic better be handled in LSP-volar? The `__init__` / `on_post_start` /...

The hacky solution that comes to mind (which I could probably do in the workflow myself) is to let PC do its thing and then overwrite the dependency in `Lib/python38`....

I did implement the hack in https://github.com/sublimelsp/lsp_utils/pull/126. Doing it in a generic way that considers all possible cases would take some more work.