-
Notifications
You must be signed in to change notification settings - Fork 734
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
fix: add warning about wrangler dev
with remote Durable Objects
#687
fix: add warning about wrangler dev
with remote Durable Objects
#687
Conversation
🦋 Changeset detectedLatest commit: b9bb4c9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2035829987/npm-package-wrangler-687 You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/687/npm-package-wrangler-687 Or you can use npx https://prerelease-registry.developers.workers.dev/runs/2035829987/npm-package-wrangler-687 dev path/to/script.js |
45eba66
to
c66d1d7
Compare
Durable Objects that are being bound by `script_name` will not be isolated from the live data during development with `wrangler dev`. This change simply warns the developer about this, so that they can back out before accidentally changing live data. Fixes cloudflare#319
c66d1d7
to
b9bb4c9
Compare
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.
Note that there are already tests in publish.test.ts
that use remote Durable Objects and check that there are no warnings rendered.
We should also follow up internally and ask for an "environment" that we can pass to the binding, so one could, for example, bind to a staging/non prod environment during dev |
Thanks @petebacondarwin ! |
Durable Objects that are being bound by
script_name
will not be isolated from thelive data during development with
wrangler dev
.This change simply warns the developer about this, so that they can back out before
accidentally changing live data.
Fixes #319