If a built next app is all Static, can I deploy it to a static hosting? and how?

[iam-yan]

Without any usage of getInitialProps, getServerSideProps and getStaticProps, the app is all Static. In this case can I deploy it to a static hosting? And how?

[rafaelalmeidatk]

You can generate static HTML with next export that can be utilized in any static hosting service: https://nextjs.org/docs/advanced-features/static-html-export

[rafaelalmeidatk]

next export is the only way to generate static HTML files, all other methods will require a Node server. I has been a while since I built a static HTML app but you need to tell your hosting service to route the dynamic URL to a HTML file, like /user/foo to the /user/[id].html file

[rafaelalmeidatk]

I also use catch all route. In this case what is the best practice to build and deploy the app into a static hosting?

I tested it but looks like the catch all routes aren't supported by next export 🤔
What you would have to do is route all the paths to a specific file, then render the page based on location.pathname. Keep in mind this will not benefit from code-splitting of individual pages since you are essentially bundling all the code from these pages into a single entrypoint

[iam-yan]

next export is the only way to generate static HTML files, all other methods will require a Node server. I has been a while since I built a static HTML app but you need to tell your hosting service to route the dynamic URL to a HTML file, like /user/foo to the /user/[id].html file

@rafaelalmeidatk I am bit confused. According to the document, the 'Static Export' is not necessary and could be replaced with regular build thanks to Automatic Static Optimization, isn't it? If so, why other methods would always require a server?

If your pages don't have getInitialProps you may not need next export at all; next build is already enough thanks to Automatic Static Optimization.

[iam-yan]

@w3bdesign Thanks. But I was trying to use firebase hosting. Do you have any idea on how to make it work?