Fully static export

[jepser]

Enable fully static export by adding the property to the configuration object.

module.exports = {
  staticMarkup: true
}

[sebastiandedeyne]

Have in mind that getInitialProps won't be called

What's the reasoning behind this? Can't it be run during export?

[jepser]

Probably I need to be clearer, @sebastiandedey by setting staticMarkup to true, instead of renderToString in the export, it will run renderToStaticMarkup, so if you do client routing, it won't work as expected (running getInitalProps).

[timneutkens]

So there are a few things that come to mind:

• This PR only implements staticMarkup for next export, it should also work in development / production mode
• staticMarkup doesn't make it immediately clear what this option does

> Have in mind that `getInitialProps` won't be called and all React bindings won't work. This will be a only html/css export.

Instead of saying getInitialProps won't be called, which is not completely true as we call it on next export, this would probably be a better explanation:

When enabling staticMarkup mode no script tags will be included in the rendered HTML, this is useful when creating a completely static application with no runtime.

[jepser]

@timneutkens that makes sense, let me update the PR.

[pengshaosu]

So there are a few things that come to mind:

• This PR only implements staticMarkup for next export, it should also work in development / production mode
• staticMarkup doesn't make it immediately clear what this option does

> Have in mind that `getInitialProps` won't be called and all React bindings won't work. This will be a only html/css export.

Instead of saying getInitialProps won't be called, which is not completely true as we call it on next export, this would probably be a better explanation:

When enabling staticMarkup mode no script tags will be included in the rendered HTML, this is useful when creating a completely static application with no runtime.

if only disable getInitialProps when call on SSR, the client side still working. how can configure?

[pengshaosu]

@

Enable fully static export by adding the property to the configuration object.

module.exports = {
  staticMarkup: true
}

this useful function is still not working/ok now?

[timneutkens]

That's what an open pull-request means yes.

[timneutkens]

I'm going to close this PR, feel free to open a new one with my feedback taken into account: #5485 (comment)

[jepser]

Sure, I'm working on that, HMR breaks as removing some scripts that are not needed when removing React, so I'm still working on solving that issue.

I saw staticMarkup property is under next-server as a flag, do you know that served the same purpose because I don't see any example? @timneutkens

[timneutkens]

Basically I want to deprecate / remove staticMarkup as we can implement other solutions for this issue that are potentially better, eg allowing the user to not load scripts or something.

[goldo]

I'm also looking for a feature like this!
For now I've forked next.js only for something that looks a bit like:
#5102

@timneutkens can you tell me more about your idea ? I'd love to help and make a PR!