-
Notifications
You must be signed in to change notification settings - Fork 115
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
https://aws.amazon.com/blogs/mobile/amplify-next-js-13/ #3511
Comments
Hi @ConsultantsCombined, thanks for reaching out to us regarding the support of Incremental Static Regeneration (ISR) for Next.js apps on Amplify Hosting. We can confirm that we support the ISR feature for Next.js apps on Amplify Hosting with both the Web Compute platform as well as the legacy Web_Dynamic platform. Today, we do not support On-demand ISR with either of the platforms and our team is working extensively to prioritize this feature for our customers: #3116 The lack of support for On-demand ISR has already been outlined in our official AWS documentation - https://docs.aws.amazon.com/amplify/latest/userguide/ssr-Amplify-support.html#supported-unsupported-features We will be closing this issue in favor of the documentation. As a reminder, please be respectful when raising issues and follow Amazon Open Source Code of Conduct. We endeavor to provide the best customer experience in a respectful and welcoming environment. Thank you! |
|
Before opening, please confirm:
App Id
Next JS - ISR - Documentation Stating Falsehoods
AWS Region
us-east-1
Amplify Hosting feature
SSR
Describe the bug
Quite simply, the documentation states here https://aws.amazon.com/blogs/mobile/amplify-next-js-13/ that ISR is available for AWS Amplify. I would like to know who decided it was legal to lie in documentation to get sales?
I have dug through tons of issues closed by some individual that seems to provide no further details on why ISR doesn't work, they just keep deflecting and saying they will update the documentation but it has been 6+ months.
Can you please provide some accurate information about whether or not you can truly support features you state are available in this ecosystem. It's pretty sad Vercel uses AWS infrastructure, and this is where we end up with AWS Amplify.
Expected behavior
Make ISR work as your documentation states or you may regret lying in your documentation.
Reproduction steps
Build Settings
Irrelevant
Log output
Irrelevant
Additional information
Irrelevant
The text was updated successfully, but these errors were encountered: