that's awesome I think we'd love to add that in officially

I've built it in a way that I keep the code very in line with the Nextjs implementation, as there is a ton of shared code. I didn't want to prematurely abstract though, but keeping it as similar as possible will allow you to do a file diff and see where the cross over is. Some of it definitely should be abstracted while a lot of it could probably be safer to keep as duplicate. Wanted to keep that work open for discussion and set out associated tasks.

It supports all the same stuff in the Nextjs construct in terms of environment variables, custom domains, function overrides, any base region deployment etc.

If you are keen I can work towards a PR so yourselves and the community can give it a wider consideration.

I think the Architect implementation runs on API Gateway, so a possible one-up there. 😜

would love a PR, @Frank knows the nextjs construct best so he'll likely review it

Ok, I'll try get one together within the coming days. 👍