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]
Minor Changes
#848
f80c801
Thanks @sommeeeer! - Ensure that the initial request.signal is passed to the wrapperrequest.signal.onabort
is now supported in route handlers. It requires that the signal from the original worker's request is passed to the handler. It will then pass along thatAbortSignal
through thestreamCreator
in the wrapper. This signal will destroy the response sent to NextServer when a client aborts, thus triggering the signal in the route handler.See the changelog in Cloudflare here.
Note:
If you have a custom worker, you must update your code to pass the original
request.signal
to the handler. You also need to enable the compatibility flagenable_request_signal
to use this feature.For example:
#850
ce5c7b4
Thanks @dario-piotrowicz! - Add option for regional cache to skip tagCache on cache hitsWhen the tag regional cache finds a value in the incremental cache, checking such value in the tagCache can be skipped, this helps reducing response times at the tradeoff that the user needs to either use the automatic cache purging or manually purge the cache when appropriate. For this the
bypassTagCacheOnCacheHit
option is being added to theRegionalCache
class.Example:
Patch Changes
#858
7233c03
Thanks @vicb! - bump @opennextjs/aws to 3.7.6See the changes at opennextjs/opennextjs-aws@v3.7.4...v3.7.6
#857
b8b38ee
Thanks @vicb! - Clean output directory beforenext build