Markdoc language server extension fails to run in VS Code about markdoc HOT 1 CLOSED

When the language server loads a schema, it literally attempts to import it, so it has to conform with the requirements imposed by the Node.js runtime for imports.

On the first line of your schema, you have something like this: import {...} from "./(components)", which is a directory import that attempts to load an index.ts file, which is not valid in a pure ES module. The schema file itself also has a .js extension, which also prevents it from being loaded as an ES module. After changing the extension to .mjs and removing both the line that imports the React components as well as the component export at the bottom I was able to get it to load successfully in the language server.

In projects that use TypeScript and couple React components with the schema, what I'd recommend is adding a build step of some kind to generate a pure schema output. You can have a TypeScript file somewhere that just imports the schema part of the configuration, and then do a standalone build of that entry point. I typically do this with esbuild in my projects.

I'm going to convert this issue to a discussion, but I will explore some options for exposing schema loading errors and see if there's something that I can do to make these kinds of issues less opaque to the end user. There should be an easy way to see when there is a schema loading exception.

from markdoc.