Open-next v3 planning

[coryasilva]

This is a discussion to track the path to fully supporting open-next v3 #182.

SST reference implementation

Issues (with relative effort and impact scores)

• [Feature] Source default server code from new folder structure .open-next/server-functions/default
  • This will allow simple use of the v3 code (resolving some outstanding issues with auth.js/next-auth@5.0.0-beta
  • This is my main drive -- I have open-next v3 working now with manual builds using this package.json script. "openbuild": "open-next build&& cp -R .open-next/server-functions/default .open-next/server-function"
  • Low effort / High impact
  • Pending PR feat: add support for open-next v3 #234
• [Feature] Support open-next v3 cache strategy with cloudfront function and hash
  • This is improve the cache-hit ratio -- see SST impl, seems simple enough
  • Low effort / Med impact
  • Pending PR feat: Allow functionAssociations overrides #237
• [Feature] Lambda@edge middleware .open-next/middleware
  • Low effort / Med impact
• [Feature] Lambda@edge API functions .open-next/functions/${key}
  • High effort / Med impact
• [Feature] Support splitting server functions .open-next/server-functions/${key}
  • High effort / Low impact
• [Feature] Warmer Warmer Function #133
  • Low effort / Low impact

Edited 2024-12-16 to revise old comments and attach PR links

[greenlynx]

I can see that #234 has been merged now, thank you. This gives our team enough functionality to be able to use Next.js 15 - is there any timeline for a new NPM package release please?

[revmischa]

Just released it, had to fix/update some projen stuff
https://github.com/jetbridge/cdk-nextjs/actions/runs/13597093776

[IsaacTrevino]

Hey Everyone! I see you've made great progress in this library. I'm looking forward to the splitting server functions feature for app/api/*, etc. I realize open-next.config.ts is not supported by this library.