vercel / next.js

The React Framework
https://nextjs.org
MIT License
125.21k stars 26.76k forks source link

`no-store` cache in nextjs config doesn't disable disk caching. #66459

Closed zerogtiger closed 3 months ago

zerogtiger commented 3 months ago

Link to the code that reproduces this issue

https://github.com/zerogtiger/AQ-Asker

To Reproduce

  1. npm install
  2. npm run dev, then open Google Chrome.
  3. Observe that the nextjs.config.mjs includes specifiers for no caching on all pages under root.
  4. (This may require some effort in setting up Supabase storage or similar) but the profile photo image will always cache. See picture below: Screenshot 2024-06-01 at 3 37 30 PM Screenshot 2024-06-01 at 3 38 25 PM Screenshot 2024-06-01 at 3 39 12 PM

(I understand the supabase overhead is slightly sophisticated, so please contact me privately if you wish to gain access to this sample project storage)

Current vs. Expected behavior

All caching is disabled, including disk cache.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020
Binaries:
  Node: 21.2.0
  npm: 10.2.5
  Yarn: 1.22.21
  pnpm: 8.15.5
Relevant Packages:
  next: 14.1.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.3
Next.js Config:
  output: N/A

warn  - Latest canary version not detected, detected: "14.1.4", newest: "15.0.0-canary.5".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue

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

Image (next/image), Middleware, Runtime

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

next dev (local)

Additional context

Tried revalidating in profile/actions.tsx, but didn't seem to do anything. Looked through the following sources with no result:

github-actions[bot] commented 2 months ago

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.