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

Next revalidate cache when no implicitly server indication #74558

Open
deeluxe74 opened this issue Jan 6, 2025 · 0 comments
Open

Next revalidate cache when no implicitly server indication #74558

deeluxe74 opened this issue Jan 6, 2025 · 0 comments
Labels
bug Issue was opened via the bug report template. Developer Experience Issues related to Next.js logs, Error overlay, etc.

Comments

@deeluxe74
Copy link

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/z5xghx

To Reproduce

  1. Start the application
  2. Go inside the api and change a product name
  3. Reload the app, the name change instantly

Current vs. Expected behavior

I expected the api call to be made on server and cache 10 seconds.
But I can see that it's not the case, it served up-to-date data.

If I add 'use server' inside product.service.ts the fetch will be executed on server and cached.

Screen_Recording_Compressed_1080p.mp4

At least the expected behavior for me, is too have a info message that the cache has been skip because the function is use inside a client-side files.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Nov 14 18:15:21 PST 2024; root:xnu-11215.41.3~13/RELEASE_ARM64_T6041
  Available memory (MB): 49152
  Available CPU cores: 14
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 15.1.3 // Latest available version is detected (15.1.3).
  eslint-config-next: 15.1.3
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

Developer Experience

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

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

No response

@deeluxe74 deeluxe74 added the bug Issue was opened via the bug report template. label Jan 6, 2025
@github-actions github-actions bot added the Developer Experience Issues related to Next.js logs, Error overlay, etc. label Jan 6, 2025
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. Developer Experience Issues related to Next.js logs, Error overlay, etc.
Projects
None yet
Development

No branches or pull requests

1 participant