Skip to content
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

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

Closed
zerogtiger opened this issue Jun 1, 2024 · 0 comments
Closed

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

zerogtiger opened this issue Jun 1, 2024 · 0 comments
Labels
bug Issue was opened via the bug report template. Image (next/image) Related to Next.js Image Optimization. Middleware Related to Next.js Middleware Runtime Related to Node.js or Edge Runtime with Next.js.

Comments

@zerogtiger
Copy link

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:

@zerogtiger zerogtiger added the bug Issue was opened via the bug report template. label Jun 1, 2024
@github-actions github-actions bot added Image (next/image) Related to Next.js Image Optimization. Middleware Related to Next.js Middleware Runtime Related to Node.js or Edge Runtime with Next.js. labels Jun 1, 2024
@zerogtiger zerogtiger reopened this Jun 16, 2024
@zerogtiger zerogtiger closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2024
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. Image (next/image) Related to Next.js Image Optimization. Middleware Related to Next.js Middleware Runtime Related to Node.js or Edge Runtime with Next.js.
Projects
None yet
Development

No branches or pull requests

1 participant