docs(nextjs): added guide for Cloudlfare OpenNext support #15652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I won't merge this yet as it partially needs getsentry/sentry-javascript#18336 to be released, but I wanted some initial opinions.
This PR adds new information about supporting Next.js deployments on Cloudflare Workers via Cloudflare's official OpenNext adapter.
During my investigation of Cloudflare Workers not sending any errors or traces for Next.js apps, I found out that it was because Cloudflare workers didn't support
https.requestmodule until recently which would've prevented the SDK from sending anything. Setting the compat date alone fixes most of the sending issues.So I wanted to document this information so users are able to find it more easily.
My findings can be verified by checking out this repo and try setting the
compatdate to anything below August 16th. You don't need a cloudflare account, justwranger devshould give you a similar environment locally to verify that.Question for reviewers: Should this live in special guides like I did here? or maybe add it to the manual setup?