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
@cloudflare/next-on-pages@1.8.6
Patch Changes
0b1af18: add assertions for making sure that the required
setupDevBindings
options are providedbb18e8a: fix: ensure Durable Object stub proxies fetch Durable Objects and not their containing Worker
Previously, calling
DurableObjectStub#fetch()
would dispatch afetch
event to the Worker containing the target Durable Object, not the Durable Object itself. This change ensures thefetch
event is dispatched directly to the Durable Object.3dd1f20: indent
setupDevBindings
warnings519c6cc: add
databaseId
variant for D1s to thesetupDevBindings
D1 binding typeD1 databases can only be referenced by their ID and not name, the current implementation
wrongly accepts the database name and uses it as the database id, in order to amend this
without introducing a breaking change we add a variant of the D1 binding type that accepts
a
databaseId
field instead of thedatabaseName
for the binding and we present a warningto users if the
databaseName
is used instead.When a better more stable/clear API will be decided for D1 bindings we can revisit this API.
05b6256: remove the invalid stringification of var bindings in
next-dev
bb18e8a: chore: bump to
miniflare@3.20231218.1
eslint-plugin-next-on-pages@1.8.6