next-redux-wrapper VS serverless-next.js

RTK Query uses another library (next-redux-wrapper) to wrap getServerSideProps and allow the usage of redux server-side.

Next.js documentation on data fetching and state Next.js documentation on server components Redux documentation Next.js Redux Wrapper documentation

That's how you can integrate Redux with a Next application! You can find the GitHub repository for this project here. I would also encourage you to review the documentation of next-redux-wrapper to learn more about other use cases.

I’d suggest reviewing the docs for the repo and see if their use cases for yours.

I try to follow the tutorial which shown on the next-redux-wrapper but no success. Nothing change.

I just hopped on this project that uses nextJS, and since most of the guys working on it were mobile devs first, we are using this library to use redux sagas.

Hi! I have never used Redux with Next.js before. I've searched for tutorials - some ignore the SSR entirely, some use something called "redux-toolkit", some use something called "redux-wrapper". All of this is confusing and overwhelming, and I don't know enough to figure out which approach is the correct one.

Since then, though, I've been working towards moving us over to a new Next.js subproject as the long-term migration plan. Right now I've got Next proxied behind the existing Express backend, and I'm using s to show Next-rendered UI inside of the legacy client. Working great so far. (I've been wanting to do a blog writeup on this for months, but haven't had time.)

I actually hadn't ever tried to use Redux with Next at all until just recently, when I added it to one specific page in the new client. My impressions are:

• The big problem is that Next codebases are set up on a per-page basis, rather than the global app setup you see in CRA or React Native. So, the Redux store setup also has to be per-page if there's different reducer logic.
• There's an assumption that you probably want to use Redux to do some SSR rendering, and then pass the initial state to rehydrate the store on the client as well. That's where tools like https://github.com/kirill-konshin/next-redux-wrapper come in.

In our case we don't have any SSR or SSG going on. I ended up borrowing some store setup logic from the existing withRedux and withReduxToolkit examples in the Next repo, but skipped all the store persistence stuff.

So, it's doable, but there's a couple additional aspects to consider beyond what you'd see in a CRA project.

I fail to see any good example of getServerSideProps and redux. I've seen this: https://github.com/kirill-konshin/next-redux-wrapper#getserversideprops. Does it make sense to trigger a redux-thunk in the example there instead of `store.dispatch({type: 'TICK', payload: 'was set in other page'});`

I'm currently waiting SST v2 to be released where they will use https://open-next.js.org instead of https://github.com/serverless-nextjs/serverless-next.js

To deploy the app, I had the requirement to use AWS as a cloud-provider, with a limited budget, so neither Vercel (a safe choice, as it is the company which develops Next.js), nor a containerized solution like the managed AWS ECS Fargate service could satisfy my needs. Then, I started with a serverless hosting thanks to the serverless-next project, which provides a serverless plugin or a CDK construct to deploy a Next.js stack. However, this project is no more well-maintained and new Next.js features (like middlewares, etc.) are not supported.

If you have the time and resources, I'd suggest to take a look at SST.dev and or OpenNext (created by the SST people). With that ISR should work (although they still seem to work on upgrading to v12). Or take a look at https://github.com/sladg/nextjs-lambda to run NextJS on a lambda exclusively.

serverlessnextjs does not support NextJS 13. https://github.com/serverless-nextjs/serverless-next.js/issues/2497

Let's mention that it's possible to deploy a Next.js application using SST 😅. This setup relies on the serverless-next.js project and it's hidden behind a construct named NextJsSite. It can be a very efficient solution when you want to ship your application on AWS environment (I use it for a production workload in my current company).

ATM Next JS is SSR (Server Side Rendering) so only S3 and CloudFront is not enough! As mentioned here already Lambda@Edge can do the server parts and is used like in Amplify. An Alternative would the serverless framework which offers a next js deployment https://github.com/serverless-nextjs/serverless-next.js .

Could this output format be used by others, to deploy to other platforms?

I currently use [1] to be able to deploy a nextjs app to AWS with API Gateway. Would be nice to have standard patterns for cloud deployments for mulitple frameworks.

[1] https://github.com/serverless-nextjs/serverless-next.js/blob...