fetch with cache: 'no-store' makes output: 'export' ignoring the page

Why this is a good first issue

Conflict between static export and dynamic fetch behavior needs investigation

AI Summary

The issue reports unexpected dynamic rendering when using fetch with 'no-store' cache option during static export. Maintainer comments suggest this may be intentional behavior. Requires understanding of Next.js static export constraints and fetch caching mechanisms.

Issue Description

Link to the code that reproduces this issue

https://github.com/dominicbachmann/next14-no-store-output-export-bug

To Reproduce

Add output: 'export' to next.config.js
Use fetch with the cache: 'no-store' option on a page
Build the application (npm run build)
Check the output
/some-page is marked as dynamic

Current vs. Expected behavior

I expect that some-page is still generated statically

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
  Available memory (MB): 9949
  Available CPU cores: 16
Binaries:
  Node: 18.19.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.81 // Latest available version is detected (14.1.1-canary.81).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: export

Which area(s) are affected? (Select all that apply)

Static HTML Export (output: "export")

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

No response

GitHub Labels

bug