Do you have a fix set of dynamic routes?

If you do, you can use function to generate the static site

In 2.13.0, `nust` introduced a `target: static` feature, make sure to 
check [it](https://nuxtjs.org/blog/going-full-static) out.

Do you care about the SEO?

If you do care the SEO, you can use SSR in Nuxt, which is the universal mode. The other choice is the above static site genration

Do you have a SPA site?

If you do, you can use spa mode and refer to the nginx setting showed here

If you don't know the exact dynamic routes, don't care about SEO for dynamic routes, you can combine the static site generation with dynamic routes.

In universal mode, use nuxt generate to generate a static site.

In the generate config, define a custom page for SPA fallback:

export default {
  generate: {
    fallback: "custom_sap_fallbackpage.html"
  }
}

Then in Nginx, define the same fallback page for unknown route, like:

location / {
    try_files $uri /custom_sap_fallbackpage.html;
}

If you set fallback: true, Nuxt will use 404.html as the default fallback page, unless you configure nginx to ignore its own default 404 page, nginx will still show you the default nginx 404 page. I think a custom fallback page is the easiest way to do the static site generation and SPA mixing.

In this approach, static page will be pre-rendered, dynamic routes is treated as unknown route for nginx, which use the fallback SPA page to render.

create a .htaccess file and put the below code into it.

<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /
  RewriteRule ^index\.html$ - [L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule . /index.html [L]
</IfModule>

npm run generate does not support dynamic routes. Because it doesn't know how to build the {{pageid}}.html.

From nuxt docs:

Dynamic routes are ignored by the generate command.

see: https://nuxtjs.org/api/configuration-generate#routes