workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
There are no special instructions for
There are no special instructions for migrating from Wrangler v2 to v3. You should be able to update Wrangler by following the instructions in Install/Update Wrangler. You should experience no disruption to your workflow.https://developers.cloudflare.com/workers/wrangler/migration/update-v2-to-v3/...
Ah ok so it looks like the order you
unstable_dev
is important here. Moving const user = await unstable_dev(...)
before const core = await unstable_dev(...)
seems to work. Would you mind opening a GitHub issue for this? We're just starting a rewrite of wrangler dev
's internals, and this is something we should consider. đź‘ŤHi i am developing a nextjs app and use
npx @cloudflare/next-on-pages@1 --watch
and npx [email protected] pages dev .vercel/output/static --compatibility-date=2023-08-14 --live-reload --compatibility-flag=nodejs_compat
in parallel. As soon as i edit a file that will be a function the recompiling leads to a crash of wrangler. Is there anything i did wrong?hi im not sure if some release went
Error: Expected "2023-08-14" but got "workerd 2023-08-01"
Wrangler Tree Shaking I m having trouble
npx wrangler deploy --dry-run --outdir dist --minify=true
or npx wrangler deploy --dry-run --outdir dist
I can clearly identify dead code that isn't needed for the worker. I've set all my ts modules to "esnext", but still no good. I also don't see any way to adust the esbuild config. Any suggestions?Hi đź‘‹ I am having an issue with
wrangler tail
that it always exits automatically after some time. Is it the expected behavior?? I didn't find any solution for this online.`connect(): Connection refused` in Vitest setup file
workerd/util/symbolizer.c++:95: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:277: info: exception = kj/async-io-unix.c++:1526: disconnected: connect(): Connection refused
workerd/util/symbolizer.c++:95: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use `--test_env=LLVM_SYMBOLIZER=<path>`.
workerd/jsg/util.c++:277: info: exception = kj/async-io-unix.c++:1526: disconnected: connect(): Connection refused
I m using KV in a similar way and was
unstable_dev
API has bindings for KV etc. in the properties, but I guess they are not wired to anything yet. Would be great if they get wired up and some methods are exposed to allow seeding and manipulating data for testing purposes....Hey there it doesn t seem possible to
unstable_dev
and pass local: false in wrangler 3.x. Whatever I try, it will still default to local: true because the code checks for args.remote only. Which probably doesn't make sense given unstable_dev
doesn't allow setting remote: true. Any idea?damn i m gonna miss fs based KV it was
We are actively working on breakpoint
Curious if anyone here uses `unstable
unstable_dev
from wrangler
(v3). I'm running into an issue and I'm not sure whether I'm just doing something wrong, or it's a legitimate bug.
When I try to enable bindings for both D1 and DO, the following error is thrown and it fails to start. However, if one is enabled and the other isn't, I don't encounter the error.
```
service core:user:worker: Uncaught TypeError: Class extends value undefined is not a constructor or null...Has anyone here ever experienced issues
wrangler dev --experimental-local
instance on a local network ip?for clarity `unstable dev` is a wrapper
unstable_dev
is a wrapper around wrangler dev
, so wrangler dev --local
corresponds to local: true
in unstable_dev
Hey there how do you access R2 bindings
unstable_dev
local: true mode? It seems it's creating fake R2 bindings.Hey there anyone using local false with
Error: Could not proxy request: TypeError: fetch failed
[pages:err] Error: Could not proxy request: TypeError: fetch failed
error all of a sudden. I thought this is an issue with the new version and so downgraded to the version (2.9.1) which I was using earlier but issue still persists. Changed the port of vite dev server to make sure that the port number is not in use already but issue still remains. What could be the reason behind this issue?and `jq` can extract super easily
jq
can extract super easily:
curl_prod accounts/:account/pages/projects/:pages-project/deployments -s | jq '.result[0].deployment_trigger.metadata.commit_hash
curl_prod accounts/:account/pages/projects/:pages-project/deployments -s | jq '.result[0].deployment_trigger.metadata.commit_hash
I m running into an `Authentication
Authentication error [code: 10000]
error when executing wrangler dev
@ 2.8.1
and I am wondering if I have the correct permission scopes to run the wrangler v2 dev command, can someone confirm if this is sufficient scoped permissions?
- account (read)
- user (read)
- workers (write)...