We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We're using nextjs but not a full featured version, should document or link out to an explanation of what the differences are https://nextjs.org/docs/advanced-features/static-html-export#supported-features
basically we dont support server side rendering / api routes, and only support static pages
can also investigate if the bundle can be separated easily from nextjs to actually deploy the service to k8s + static pages on cdn
The text was updated successfully, but these errors were encountered:
Can you please elaborate more on the issue and what is required.
Sorry, something went wrong.
Yeah goal for now is just to update https://github.com/commit-app-playground/frontend-template/blob/main/templates/README.md so it lets users know even though Next.js supports server-side rendering and API routes, our template is designed only to build a static bundle therefore only supports https://nextjs.org/docs/advanced-features/static-html-export#supported-features
No branches or pull requests
We're using nextjs but not a full featured version, should document or link out to an explanation of what the differences are
https://nextjs.org/docs/advanced-features/static-html-export#supported-features
basically we dont support server side rendering / api routes, and only support static pages
can also investigate if the bundle can be separated easily from nextjs to actually deploy the service to k8s + static pages on cdn
The text was updated successfully, but these errors were encountered: