ref(cloudflare)!: Remove wrapRequestHandler from main entrypoint - #22881
Merged
Conversation
JPeer264
requested review from
isaacs,
mydea,
nicohrubec and
s1gr1d
and removed request for
a team
July 30, 2026 17:06
nicohrubec
approved these changes
Jul 31, 2026
Member
|
@JPeer264 approved but unit tests are failing |
JPeer264
force-pushed
the
jp/remove-wrap-request-handler
branch
from
July 31, 2026 07:48
9798082 to
e417a61
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
JPeer264
force-pushed
the
jp/remove-wrap-request-handler
branch
from
July 31, 2026 09:41
ad6f938 to
8b571d0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
closes #22367
This export from the main entrypoint only leads to confusion - the
wrapRequestHandleris/was exported here and has a dedicated entrypoint in@sentry/cloudflare/request. The only reason for this export is for Oxygen runtimes, or internal use cases. For internal use cases it is ok to also import from the other entrypoint.