Skip to content

refactor: Do not prevent cache interception #370

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

Merged
merged 1 commit into from
Feb 12, 2025
Merged

Conversation

vicb
Copy link
Contributor

@vicb vicb commented Feb 12, 2025

  • Do not prevent setting config.dangerous?.enableCacheInterception to true
  • Do not explicitly disable it in templates (but it is still disabled by default)

ref: opennextjs/opennextjs-aws#738

Copy link

changeset-bot bot commented Feb 12, 2025

⚠️ No Changeset found

Latest commit: 458db2c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

pkg-pr-new bot commented Feb 12, 2025

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@370

commit: 458db2c

@vicb
Copy link
Contributor Author

vicb commented Feb 12, 2025

Thanks James!

@vicb vicb merged commit e1845d9 into main Feb 12, 2025
7 checks passed
@vicb vicb deleted the cache-interception branch February 12, 2025 08:42
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.

2 participants