Feature: Automatic Static Optimisation

[danielcondemarin]

Motivation

Nextjs 9 introduced Automatic Static Optimisation as per this RFC.

What does this mean for this serverless plugin?

This should reduce the number of Lambda functions provisioned by the plugin. Next 9 prerenders static pages as HTML files, which means this plugin could simply upload these to S3 and route the page requests via API Gateway or CloudFront.

Proposal

Given the following app:

pages/
├── stars.js
└── about.js

function Stars({ stars }) {
  return <main>Stars: {stars}</main>;
}

Stars.getInitialProps = async ({ req }) => {
  const res = await fetch("https://api.github.com/repos/zeit/next.js");
  const json = await res.json();
  return { stars: json.stargazers_count };
};

export default Stars;

function About() {
  return <main>Simple static about page. No server side stuff happening</main>;
}

export default About;

The above app produces the following built pages:

.next/serverless/pages/stars.js
.next/serverless/pages/about.html

The plugin will upload about.html to the assets bucket.
Requests to /about will be routed to S3 the same way assets are currently served by the plugin.

Requests to /stars would work as per current behaviour.

[romainquellec]

This PR is awesome as a lot of project has static/marketing pages.

[RichiCoder1]

For the implementation, would this be be filtering out .html from getNextPagesFromBuildDir and then adding another accumulator to addCustomStackResources that scans the pages dir and generates api-gw-proxy for all the .html pages it finds? Would risk hittin the resource limit, but I think that's a risk already.

[danielcondemarin]

For next 9 support use the newly released component 🙏 https://github.com/danielcondemarin/serverless-next.js