Langauge-server not starting with proper schema file #500
Replies: 2 comments 2 replies
-
Thinking about it a bit more, I am realizing I probably am never loading my schema file at all because I am not even able to load the config. Looking at recent changes in the So I am fairly certain the linked recent change is a bug. I will attempt to rollback (how to do that... 🤔) and see if that fixes the issue and report back |
Beta Was this translation helpful? Give feedback.
-
Okay, I confirmed this is just a bug due to recent regression in the language server code, I have created the following pull request: |
Beta Was this translation helpful? Give feedback.
-
I am working with the markdoc language server but am unable to get it to start with the following exception:
Looking at previous issues, it seems like in most cases, this is due to an invalid schema file that cannot be loaded into a vanilla node process. Here is the relevant context:
markdoc.config.js:
My lang-server.js file:
And here I can see that being imported into node:
I have attempted to trace the code and see if I get any exceptions in loading the file, but so far, I haven't been able to even see the load function even being called! I did this by manually modifying my locally installed copy of the extension and just added a
console.log
to the top of that load function.I have also done the same trick for seeing where the exception is thrown and added logging to the server function and the object I get back from the
connect
function does not have a config key and instead the options object only has adispose
function.I actually tried this with a very basic project and had the same issues, so I am wondering if there is some something higher up in the chain that is causing these issues!
Beta Was this translation helpful? Give feedback.
All reactions