-
Notifications
You must be signed in to change notification settings - Fork 1k
Various fixes/improvements around remote bindings being used as local #11162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…a `wrangler dev --local`
…ommand to clarify that it disables remote bindings, also un-deprecate and un-hide it
🦋 Changeset detectedLatest commit: 3db45f9 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
… dev` command to clarify that it disables remote bindings, also un-deprecate and un-hide it fix incorrect implementation
…ndingsOnly is set
wrangler dev's --local flag…emote aspect of remote bindings
160ed68 to
ba50b6a
Compare
|
I think we should unify flags with the Vitest integration, which AFAIK uses |
you're right, I thought we completely removed that when we released remote bindings 😕 Ok, thanks 🙂, I can use |
fixtures/get-platform-proxy-remote-bindings/tests/remote-bindings-false.test.ts
Outdated
Show resolved
Hide resolved
fixtures/get-platform-proxy-remote-bindings/tests/remote-bindings-false.test.ts
Outdated
Show resolved
Hide resolved
packages/wrangler/e2e/remote-binding/start-worker-remote-bindings.test.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Somhairle MacLeòid <[email protected]>
| }); | ||
| } | ||
|
|
||
| describe.only("remote bindings disabled", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.only?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, ignore it, I'm just trying to debug a CI windows failure 😓 (before just adding a skipIf(process.platform === 'win32') 😅 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I ended up just skipping the test on windows: https://github.com/cloudflare/workers-sdk/pull/11162/files#diff-d9b32f69a202cbf69dc77c2777a78758abe37967f4015456c65d005d6117c33dR146-R150
penalosa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good, with some nits
46d6edb to
dbdb75a
Compare
aae4e2b to
fa36841
Compare
This PR introduces various fixes/improvements around disabled remote bindings, namely:
wrangler dev's--localflag's description to clarify that it disables remote bindings. It also undeprecates it and un-hides it.wrangler dev --localcurrently prints local bindings (configured withremote: true) as remotewrangler dev --localremote: falseset instartWorkerdisables remote bindingsremoteBindingsoption togetPlatformProxyand also to the vite plugin to disable the remote aspect of remote bindings (aligned with vitest-pool-workers)wrangler dev,getPlatformProxyand the vite plugin cloudflare-docs#26265