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
Comments
Hi @eerison That's the right place for this question. |
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). |
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 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. 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). And, finally a template engine (tbd) to give more control on the output, and possibly generate other format than markdown. |
Super excited for this! This would work really well with Nextra's Docs Theme |
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?
The text was updated successfully, but these errors were encountered: