hey @Frank (I think this is probably your domain, correct me if wrong), I am considering a construct to handle Next.JS Static exports, but handling the routing logic in Cloudfront for dynamic routes (

[id].tsx

). • Have you thought about this? • Do you think there is value and would SST have interest in such a thing? On the face of it, it would allow a simple, cheap entrypoint to Next.JS with capabilities more or less on par with something like CRA and Next.JS defaults and static exporting (not a SPA, but real static site). It would be devoid of features listed here.

hey @Derek Kershner, yeah that makes sense. Can this construct be built on top of

StaticSite

?

I will definitely look into using what currently exists in SST as much as possible, including trying to integrate your ideas regarding seamless deployments by intelligently separating html and static js.

Haha, the standard Next.js build does that automatically. Not sure if static export does something similar.

they are in separate folders, but I meant deploying them in separate behaviors and only updating the html one.

Yup yup

alright, just wanted to check with you before I researched, don’t wanna drop something on you guys that you would hate to support. Thanks, @Frank.

Yeah, once you get it to work, it’s likely we first put it out as an example first. And if more ppl ask for this, we will create an SST construct out of it, perhaps named

NextjsStaticSite

or

NextjsExportStaticSite

lol to make it less confusing with the existing construct.

let’s say IF I get it to work, lol.

Hey @Derek Kershner, is it that you need to read from

routes-manifest.json

in order to configure the CloudFront distribution accordingly? I wonder if

Lazy

helps in this case:

const site;

site = new StaticSite(this, "Site", {
  path: "path/to/src",
  buildOutput: "dist",
  buildCommand: "npm run build",
  cfDistribution: Lazy.any({
    produce(context) {
      const file = fs.readFileSync("path/to/routes-manifest.json");
      return {
        defaultBehavior: { ... },
        additionalBehaviors: { ... },
      };
    }
  }),
});

So inside

Lazy.any

, if you reference

site.s3Bucket

, then

produce

will get called after

site.s3Bucket

is created. At this point, the site has been built and

routes-manifest.json

should exist.

That totally worked. I am working out one more edge case, then I should be fully functional.