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

Using export dynamic = 'auto' opts you into dynamic rendering #65799

Open
MangoMarcus opened this issue May 15, 2024 · 0 comments
Open

Using export dynamic = 'auto' opts you into dynamic rendering #65799

MangoMarcus opened this issue May 15, 2024 · 0 comments
Labels
bug Issue was opened via the bug report template. Performance Anything with regards to Next.js performance. Runtime Related to Node.js or Edge Runtime with Next.js.

Comments

@MangoMarcus
Copy link

Link to the code that reproduces this issue

https://github.com/MangoMarcus/nextjs-dynamic-auto

To Reproduce

  1. Clone the repository. There's a seperate route for each of the options for dynamic, plus one for none.
  2. Deploy to Vercel
  3. Check the "Deployment summary" under the deployment.
  4. The /none route is an ISR function, but /auto isn't

Current vs. Expected behavior

I expected the default for dynamic to be 'auto', but using that actually opts you in to dynamic rendering - which is not the same behavior as omitting the export altogether.

Provide environment information

Operating System:
  Platform: macOS
  Chip: Apple M1 Pro
  Version: macOS 14.4
Binaries:
  Node: 20.2.0
  npm: 9.6.6
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.3
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

Performance, Runtime

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

Vercel (Deployed)

Additional context

Screenshot 2024-05-15 at 15 45 55
@MangoMarcus MangoMarcus added the bug Issue was opened via the bug report template. label May 15, 2024
@github-actions github-actions bot added Performance Anything with regards to Next.js performance. Runtime Related to Node.js or Edge Runtime with Next.js. labels May 15, 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. Performance Anything with regards to Next.js performance. Runtime Related to Node.js or Edge Runtime with Next.js.
Projects
None yet
Development

No branches or pull requests

1 participant