workers-help
pages-help
general-help
durable-objects
workers-and-pages-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-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
vite-plugin
I'm trying to get my local d1 database
I'm trying to get my local d1 database from one local project to another local project, i.e., from one dir to another dir without re-running the
wrangler d1 execute --local --file=.sql approach. I thought I could just move the .wrangler/state/v3/d1 dir over to another dir and spin things up but that did not work. Is there some other approach I could use?
My problem is that I use a separate worker to load portions of the database and I was hoping to avoid moving that worker and its config over to another dir temporarily to get the database fully loaded.
Thanks!...Is it possible to configure wrangler to
Is it possible to configure wrangler to open something other than
localhost when working locally?
[wrangler:inf] Ready on http://localhost:8788, I'd like it to open a local alias instead of localhost but still maintain the protocol and port, e.g., http://<local-alias>:8788... it's mainly to get around CORS stuff 🙄...That sounds like you have a library
That sounds like you have a library which is trying to use an unsupported field (
credentials). Whilst browsers support that, Workers don't.hello, kind of new in the game but it
hello, kind of new in the game but it seems since the last version of wrangler (or something else) that the
workerd serve on my computer stays in a running state all the time. Is there a trick I don't know about. right now I need to kill it manuallyCould a `metafile` option be added to
Could a
metafile option be added to wrangler deploy to expose esbuild's metafile? I see that wrangler uses it internally, but it isn't exposed anywhere so you can't use standard tools to do bundle size analysis
Wranger uses esbuild under the hood (
Wrangler uses esbuild under the hood (https://developers.cloudflare.com/workers/wrangler/bundling/).
Is there a way to configure it to output the esbuild meta file (https://esbuild.github.io/api/#metafile) to better understand the bundle it creates?...
Logpush · Cloudflare Workers docs
Hey guys, anyone have info on how to enable Workers Trace Events Logpush? I'm on workers Paid plan and always getting "Access Denied" when runing the command to enable logpush to R2, but trying to list the logpush jobs returns an empty list using the same credentials, I also can't find the menu "Analytics & Logs > Logs" as stated in the docs: https://developers.cloudflare.com/workers/observability/logpush/
Hello, I have a question about `keep_
Hello, I have a question about
keep_vars option, is it supposed to only prevent variables that exist in the dashboard but not in Wrangler from being deleted, or also prevent same variables from being overridden?
My issue is that I'm trying to find a way to prevent vars in dashboard from being overridden by wrangler when deploying, is it possible?...i am using `wrangler pages dev ./public`
i am using
wrangler pages dev ./public to run a CF page locally and none of the shortcut works │ [b] open a browser, [d] open Devtools, [c] clear console, [x] to exit . idea? wrangler 3.15.0.🐛 BUG: Wrangler throwing an error fails...
@Adam, sorry for the ping - is https://github.com/cloudflare/workers-sdk/issues/3696 the mentioned port in use race condition? :p
Wrangler DX feedback
Hey devs, we'd love to hear your feedback on the @Wrangler CLI development experience, if you'd like to help us improve it, please share your feedback in this thread
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
Ah ok, so it looks like the order you call
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
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
hi im not sure if some release went weird or I need to wait but i'm trying to install wrangler@latest and i'm getting
Error: Expected "2023-08-14" but got "workerd 2023-08-01"Wrangler Tree Shaking I m having trouble
Wrangler Tree Shaking: I'm having trouble with tree shaking my workers when I bundle via wrangler. Does this happen by default or do I have to enable it? When I run
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
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
i'm getting
...
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