Next export broken in 13.3.1 (app dir)

[re-thc]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 20.0.0
      npm: 9.4.0
      pnpm: 8.3.1
    Relevant packages:
      next: 13.3.1
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Static HTML Export (output: "export")

Link to the code that reproduces this issue

N/A

To Reproduce

next build

Describe the Bug

html files are missing from the output

Expected Behavior

html files should be present (works if degrade to 13.3.0)

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[samulisuomi]

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Static HTML Export (output: "export")

Just making sure: in next.config.js, did you add output to the root of nextConfig or inside experimental? I did the latter and was confused for a while.

I.e. this does not work:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    appDir: true,
    output: 'export',
  },
}

module.exports = nextConfig

This does work for me:

```tsx
/** @type {import('next').NextConfig} */
const nextConfig = {
  output: 'export',
  experimental: {
    appDir: true,
  },
}

module.exports = nextConfig

[re-thc]

@samulisuomi outside of experimental.

It works for 13.3.0 and only broke on 13.3.1 and it actually builds just doesn't output html (does output js/css).

[samulisuomi]

Hmm... Very strange. I'm on 13.3.1 too and it does work.

That's what I get after changing my config and running npm run build (== next build). Fwiw I don't use page folder at all – just app – and the app itself is a very small dummy demo app for a workshop at my job.

I do encounter other issues with the app folder + static export combo myself (related to dynamic route segments) but the HTML files themselves are exported to out.

Just a long shot but what if you upgrade to the later next version and run npm ci (that nukes node_modules) and then retry next build?

[re-thc]

@samulisuomi perhaps it is related to dynamic routes. Due to i18n all my routes are in dynamic segments / getStaticParams. No luck with nuking.

[samulisuomi]

@re-thc here’s a related issue I’ve been following, not sure if it helps: #48022