Force static HTML export

[kr8n3r]

Hi 👋
we're looking to build performant product pages using mdx, so looking at static HTMl export.
However, running next build && next export, outputs as SSG

which is less than ideal, as we'd need to include legacy IE polyfills.

Any ideas what config we'd be missing?

Link to repo: https://github.com/alphagov/paas-product-pages

[Timer]

Not sure I understand your question. SSG and next export are nearly analogous!

next export loses some benefits though, i.e. Incremental Static (Re)Generation.

[kr8n3r]

so nextJS framework requires history api to work properly?
trying to understand if we're not using intentionally initial props, can we not just export plain html

[Timer]

Next.js requires the history API for client-side transitions to work: the same as any JS framework. This is what the JSON file is used for.

Since you want to disable JavaScript for IE8 support, every transition will be server-side, meaning your visitors will only be getting HTML.

I'd suggest going through the Next.js tutorial to learn how Next.js works, as it answers a lot of your questions.

[kr8n3r]

appreciate your help and as I understand, to trully have a no-js running site, the config you provided is the only way to achieve that?

[Timer]

The config I provided is the only way to run a no-JS site, correct.

You could always manually post-process the out/ directory to remove all <script> tags, too.

[kr8n3r]

thanks @Timer