Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support nextjs #793

Open
eerison opened this issue Mar 11, 2023 · 4 comments
Open

support nextjs #793

eerison opened this issue Mar 11, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@eerison
Copy link

eerison commented Mar 11, 2023

Sorry if it isn't the appropriate place to ask this.

But is there any plan for this lib support nextjs? or is it already possible to use it there?

@eerison eerison added the enhancement New feature or request label Mar 11, 2023
@edno
Copy link
Member

edno commented Mar 22, 2023

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.

@edno edno added this to the 2.0.0 milestone Mar 26, 2023
@LunaticMuch
Copy link

LunaticMuch commented Mar 27, 2023

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
Copy link
Member

edno commented Aug 30, 2023

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

4 participants