enable getCloudflareContext to also work with next dev
#33
Conversation
This file contains 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
dario-piotrowicz
force-pushed
the
get-cloudflare-context-dev
branch
2 times, most recently
from
80773ad to
0e08459
Compare
dario-piotrowicz
force-pushed
the
get-cloudflare-context-dev
branch
from
16d9eaf to
26bc5bb
Compare
dario-piotrowicz
force-pushed
the
get-cloudflare-context-dev
branch
from
b198749 to
a88b42e
Compare
vicb
approved these changes
Sep 25, 2024
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Followup for #31 there we introduced
getCloudflareContextin a way that would work only in production/preview, this PR adds support for it undernext dev(viagetPlatformProxy)