[NEXT-1030] `output: 'export'` with `use client` in dynamic routes doesn't work

[qpre]

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: 18.13.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.2.5-canary.32
      eslint-config-next: N/A
      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

https://github.com/qpre/next-app-dir-dynamic-with-static-export

To Reproduce

• run yarn install
• run yarn build
• open the out folder and see that static pages are rendered but /toto/[toto].html is missing, based on the docs it should be exported.

Describe the Bug

static routes are exported but the ones with dynamic params are not.

Expected Behavior

based on the docs dynamic routes using 'use client' should be exported.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1030

[ivoiv]

Can confirm.
I'm still trying to find a version in which this actually works.

The .js files for the dynamic pages are actually in the out/_next/static/chunks/app folder but the root index just doesn't do any routing to them when the page is requested.

[abduraufsherkulov]

Issue still persists in 13.3.1-canary.0 @qpre

[hyunjunian]

I am looking forward to this feature very much. Please check and resolve this problem!

[johnny-mh]

Same here (13.3.1-canary.5)

[klcantrell]

I pulled down the repro project and upgraded it to 13.3.1-canary.7. In addition to the issues described above, I notice that next build outputs the dynamic route as server-side rendered:

Route (app)                                Size     First Load JS
┌ ○ /                                      178 B          80.2 kB
├ ○ /about                                 178 B          80.2 kB
├ ○ /toto                                  141 B          74.7 kB
└ λ /toto/[toto]                           736 B          75.3 kB        <-- here 
+ First Load JS shared by all              74.5 kB
  ├ chunks/2443530c-d36173516156a79f.js    50.5 kB
  ├ chunks/961-410119e98d707b91.js         22.2 kB
  ├ chunks/main-app-4fd98d23d091d9e6.js    213 B
  └ chunks/webpack-8074fabf81ca3fbd.js     1.61 kB

Route (pages)                              Size     First Load JS
─ ○ /404                                   178 B            86 kB
+ First Load JS shared by all              85.8 kB
  ├ chunks/main-c0915425be0ab499.js        84 kB
  ├ chunks/pages/_app-c544d6df833bfd4a.js  192 B
  └ chunks/webpack-8074fabf81ca3fbd.js     1.61 kB

λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)

[qpre]

The issue is still present in the latest canary (13.3.1-canary.12 at the time of writing).

My only interrogation is if it is on the roadmap for 13.3.1 or if we should just find another way until the subject comes up in vercel's roadmap (which would be perfectly fine seeing the amount of work they put in the new features at the moment, but maybe the beta docs should be updated as to not mislead someone who would invest time in trying this feature :)).

[stefan-b314]

Hi, I am also running into this issue here.
Thanks for looking into it, @styfle!