Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Next.js@RC] dynamic/static rendering depends on whether no-store is specified or is the default. #66240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AkifumiSato opened this issue May 27, 2024 · 1 comment
Labels
bug Issue was opened via the bug report template. Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation.

Comments

@AkifumiSato
Copy link
Contributor

AkifumiSato commented May 27, 2024

Link to the code that reproduces this issue

https://github.com/AkifumiSato/nextjs-issue-demo-explicit-specification-no-store

To Reproduce

  1. pnpm clean-start.
  2. access http://localhost:3000/default, todo content is fixed.
  3. access http://localhost:3000/no-store or http://localhost:3000/force-dynamic, todo content is dynamic.

Current vs. Expected behavior

I think it should be as documented, or the documentation should be corrected.

https://rc.nextjs.org/docs/app/api-reference/functions/fetch#optionscache

Next.js fetches the resource from the remote server on every request without looking in the cache

ref: #66209

Provide environment information

$ pnpm next info

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 9.8.0
  Yarn: 1.22.22
  pnpm: 8.15.7
Relevant Packages:
  next: 15.0.0-rc.0 // Latest available version is detected (15.0.0-rc.0).
  eslint-config-next: N/A
  react: 19.0.0-rc-935180c7e0-20240524
  react-dom: 19.0.0-rc-935180c7e0-20240524
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

Navigation

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

next build (local), next start (local)

Additional context

No response

@AkifumiSato AkifumiSato added the bug Issue was opened via the bug report template. label May 27, 2024
@github-actions github-actions bot added the Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation. label May 27, 2024
@AkifumiSato
Copy link
Contributor Author

Document updated, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template. Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation.
Projects
None yet
Development

No branches or pull requests

1 participant