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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@opennextjs/[email protected]
Patch Changes
#320
ff2dd55
Thanks @james-elicx! - feat: d1 adapter for the tag cache#409
a604c85
Thanks @dario-piotrowicz! - make sure that instrumentation files workcurrently instrumentation files
in applications built using the adapter are ignored, the changes here
make sure that those are instead properly included in the applications
#410
d30424b
Thanks @dario-piotrowicz! - removeeval
calls introduced bydepd
wrapped functionsSome dependencies of Next.js (
raw-body
andsend
) usedepd
to deprecate some of their functions,depd
useseval
to generate a deprecated version of such functions, this causeseval
warnings inthe terminal even if these functions are never called, the changes here by patching the depd
wrapfunction
function so that it still retains the same type of behavior but without using
eval
#404
12d385d
Thanks @dario-piotrowicz! - fix incorrect (sync)getCloudflareContext
error messagecurrently
getCloudflareContext
run in sync mode at the top level of a not static routegives a misleading error message saying that the function needs to be run in a not static
route, the changes here correct this error message clarifying that the problem actually is