Closed deathaxe closed 4 months ago
Thank you for reporting this issue, we'll take a look!
The package-lock.json
in your project seems to be pointing to an old version of our dependencies: https://github.com/sublimelsp/LSP-astro/blob/9f9f6f4f8c15687169124f5f1c47c4b3e17ded38/language-server/package-lock.json#L626
We use the volar-2.4
tag on all of these: https://github.com/withastro/language-tools/blob/9e457653f59f3ffa9fa492145c56fd027b577217/packages/language-server/package.json#L33-L38, which at the time of writing points to 0.0.59. Maybe updating that lockfile would fix the problem.
Thanks for the quick reply.
I always relied on dependabot to do its job, but as it seems it didn't do that thoroughly enough.
Manually re-running npm upgrade
fixed failing start.
Sorry for the noise.
Describe the Bug
The following initialization request is made by Sublime Text 4's LSP plugin with a simple dummy astro project open, causing language server to crash while starting
Server seems to fail initializing
selectionRangeProvider
. However disabling this capability client-side doesn't resolve / work around this issue.Nothing changed but https://github.com/sublimelsp/LSP-astro/commit/9f9f6f4f8c15687169124f5f1c47c4b3e17ded38
Server starts properly with a commit before, running astro language server 2.10.x
Steps to Reproduce
{'code': -32603, 'message': "Request initialize failed with message: Cannot read properties of undefined (reading 'selectionRangeProvider')"}