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

https://aws.amazon.com/blogs/mobile/amplify-next-js-13/ #3511

Closed
5 tasks done
PythonCircuit opened this issue Jun 3, 2023 · 2 comments
Closed
5 tasks done

https://aws.amazon.com/blogs/mobile/amplify-next-js-13/ #3511

PythonCircuit opened this issue Jun 3, 2023 · 2 comments
Assignees
Labels
Next.js question Further information is requested

Comments

@PythonCircuit
Copy link

Before opening, please confirm:

  • I have checked to see if my question is addressed in the FAQ.
  • I have searched for duplicate or closed issues.
  • I have read the guide for submitting bug reports.
  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

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

  1. Setup nextjs app with amplify
  2. Enable SSR
  3. Setup ISR
  4. Deploy
  5. Lies

Build Settings

Irrelevant

Log output

Irrelevant

Additional information

Irrelevant

@PythonCircuit PythonCircuit added bug Something isn't working pending-triage labels Jun 3, 2023
@nadetastic nadetastic self-assigned this Jun 5, 2023
@Jay2113
Copy link
Contributor

Jay2113 commented Jun 5, 2023

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!

@Jay2113 Jay2113 added question Further information is requested and removed bug Something isn't working pending-triage labels Jun 5, 2023
@Jay2113 Jay2113 closed this as completed Jun 5, 2023
@github-actions
Copy link

github-actions bot commented Jun 5, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@aws-amplify aws-amplify locked as resolved and limited conversation to collaborators Jun 5, 2023
@Jay2113 Jay2113 self-assigned this Jun 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Next.js question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants