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

Please create documentation for Next.js 13 and beyond. #5840

Open
qwikag opened this issue Sep 3, 2023 · 5 comments
Open

Please create documentation for Next.js 13 and beyond. #5840

qwikag opened this issue Sep 3, 2023 · 5 comments
Assignees
Labels
amplify/js Issues tied to JS

Comments

@qwikag
Copy link

qwikag commented Sep 3, 2023

Describe the content issue:
Please create documentation for Next.js 13 and beyond. separate App Router from Pages Router, they need to be 2 separate documents, and both include everything.

This experience with Amplify & next.js 13 has been the most god-awful experience of my 30 years in IT.

URL page where content issue is:
API with Server-Side Rendering (SSR)

@abdallahshaban557
Copy link
Contributor

Hello @qwikag - we have added some temporary documentation for how to use the App router and Pages router in our documentation here https://docs.amplify.aws/lib/ssr/q/platform/js/.

We are not happy with our current experience, and we are currently planning to revamp that as part of our next major version. We will also make sure our documentation is comprehensive for all functionality of NextJS 13 including RSC and App Router, Server Actions, Middleware, API routes. Please feel free to leave us feedback on our Focus areas for Q4 of 2023 RFC here.

@qwikag
Copy link
Author

qwikag commented Sep 3, 2023

It probably doesn't help that at the top it says:
"
SSR functionality in Amplify was primarily built for compatibility with Next.js page components, and their getServerSideProps data fetching mechanism. Compatibility with other frameworks or Next.js features cannot be guaranteed.
"
It is a fair statement but it causes a person to read and then walk away.

I get that it is temporary, and I will continue on.
I would be happy to get involved in testing these new documents as or before they are released.

@qwikag
Copy link
Author

qwikag commented Sep 4, 2023

@abdallahshaban557 could you please point me at something worthy to aid querying and mutating data, that is javascript based, everything worthwhile uses typescript.

this page you pointed me seems to confuse 13.4+ with prior versions.
I have all the frontend working with Tailwind, Auth, App Routing, I have 2 remaining capabilities to work out: Data and Swipe.
Also connecting cognito Users with the data is also a complex topic that is not well discussed.

@qwikag
Copy link
Author

qwikag commented Sep 4, 2023

A good example of being not helpful is the fact that the example does not annotate 'use client' at the start making it error. not to mention the received error does not refer to anything in that code that is fixable.

@josefaidt josefaidt added the amplify/js Issues tied to JS label Sep 8, 2023
@cwomack
Copy link
Member

cwomack commented Sep 12, 2023

@qwikag, this feedback is appreciated and will be reviewed with the team prior to releasing the Next.js documentation improvements! Regarding the use client part, you're specifically referencing the #1 Section within the "Getting Started with SSR page", correct? Looks like both that as well as the Tutorial could use updates and clarity on this aspect.

As for the JavaScript vs. TypeScript examples for querying and mutating data, can you take a look at our examples within the GraphQL docs for fetching data? Let me know if that helps clear things up or if there's further feedback after reviewing it.

@cwomack cwomack self-assigned this Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amplify/js Issues tied to JS
Projects
None yet
Development

No branches or pull requests

4 participants