How does cdk-nextjs compare with SST about cdk-nextjs HOT 2 CLOSED

@revmischa can chime in. We had this discussion on the sst discord. For me personally, I'm using sst's NextjsSite v2, which uses open-next. That library has taken a lot of reference from what Mischa, et all has done. I've been testing and helping out w/ sst's NextjsSite v2 to get it to a stable release. There's still some kinks to fix but it's pretty close to getting released.

from cdk-nextjs.

I was imagining that after open-next was created, this construct could make use of it and then SST would use cdk-nextjs. Then people could use open-next if they don't use CDK, they could use cdk-nextjs if they don't use SST, or they could use SST.

While Frank and SST have generously built and provided open-next to the community, they understandably are more concerned right now with applying it to SST and not CDK users at large, so open-next is directly used by SST at this point in time.

So our options are to maintain this construct for users of CDK who do not use SST, suggest to anyone that wants to use NextJS with CDK to avail themselves of SST as Mr. @khuezy has taken it upon himself to do, or rewrite this construct to make use of open-next.

Since open-next is still being worked on (my understanding is that next-auth doesn't work with it at present) I am continuing to use cdk-nextjs, but as I am an avid SST user I will probably switch to SST's NextjsSite v2 at some near future date.

If there is interest is using CDK with NextJS without using SST then this module could be useful to some people. Ideally someone would rewrite it to use open-next for building. I am not especially inclined to do this myself.

from cdk-nextjs.