support nextjs about graphql-markdown

[edno]

Hi @eerison

That's the right place for this question.
I have plan to make the solution more agnostic, ie not dependent on Docusaurus.
The work is in progress, and I expect to have something by early summer.

[LunaticMuch]

I am working on this too within my company. We have a prototype ready and working which will go out in some weeks (nothing yet finalized).
We reused @graphql-markdown/utils for parsing schema and then we generate routes and return props. We're dealing with caching now to speed up some of the elaboration.

[edno]

I have plan to make the solution more agnostic, ie not dependent on Docusaurus.
The work is in progress, and I expect to have something by early summer

Work is still in progress. Most of the ground work has been done, ie clean up the code and migrating to TS, adding documentation in the code. This is currently available in 1.21.0-next.0 and following (pre-releases only).

I am exploring the next step that is moving away from a messy architecture (the latest clean up improve the code, but not the architecture), to a cleaner one based on NestJS. I don't know yet if NestJS will be the final solution, but I will for sure move the code into a "mature" NodeJS framework offering a better code structure, and DI.
A top of it, I'll add more API documentation, so one can quickly reuse the libraries for custom export format.
👉 This will be the 2.0.

Once the framework migration is done with feature parity to current 1.x, the next steps will be moving away from the current homemade schema parser to a proper AST parser (exploration has already be done, it is just a matter of implementation).
👉 This will be the 2.0 or 2.1.

And, finally a template engine (tbd) to give more control on the output, and possibly generate other format than markdown.
👉 This will be the 2.1 or 2.2.

[nathanchapman]

Super excited for this! This would work really well with Nextra's Docs Theme