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

fix: enable cache only for clientDb #2425

Merged
merged 4 commits into from Dec 12, 2023
Merged

Conversation

Barbapapazes
Copy link
Contributor

πŸ”— Linked issue

fix #2415

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Enable the /api/cache.json endpoint only for the clientDb feature. Otherwise, it's unnecessary and can be a real pain (build perf and deployment) for huge website.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@farnabaz
Copy link
Member

Disabling it has side effect. What we can do for now is to add a flag to disable it.
In next major version, this behavior will change, and we will remove this big chunk.

Copy link
Member

@farnabaz farnabaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks ❀️

@farnabaz farnabaz merged commit f76ed94 into nuxt:main Dec 12, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Edge/Cloudflare Deployments fail due to api/_content/cache.123.json size
2 participants