No, I mean does it not work if you just **don’t** provide a Zone ID, but just the route itself?
No, I mean does it not work if you just don’t provide a Zone ID, but just the route itself?
JIt doesn't work, it gets invalid_script_name error, similar to this: https://community.cloudflare.com/t/pointing-subdomain-to-worker-route-question/98683
HWhat is the name of your Worker(directly from your
wrangler.tomlDon't worry about, I figured out a different way to solve this.
HHi,
wrangler versions
JIf this is the right place to leave Wrangler feedback, I found it aggravating that for the 3 methods below, you must specify names to them differently in order to end up with the same final resource name:
For more consistency, kv could simply 1.) use the name provided, and 2.) throw an error if a resource with that name already exists--just as the other methods do.
- d1 and r2 behave consistently with each other and use the name provided: e.g.
mysite-staging - kv is inconsistent with these and automatically preprends the name property from
, aswrangler.toml
, or<nameFromWrangler>-<nameSpecified>
if outside a dir containingworker-
.wrangler.toml
For more consistency, kv could simply 1.) use the name provided, and 2.) throw an error if a resource with that name already exists--just as the other methods do.
JUnrelated: happy to see a
wrangler.json
AIs there a way to prevent
However, if you're writing documentation or something more static than dev work, and want to reference the flow of this command, it effectively breaks that - and perhaps you're using X and it gets removed in future.
In my particular case, it's going to go into printed material, and I've been using
npm create cloudflare@2.21.1However, if you're writing documentation or something more static than dev work, and want to reference the flow of this command, it effectively breaks that - and perhaps you're using X and it gets removed in future.
In my particular case, it's going to go into printed material, and I've been using
2.21.1
npm create cloudflare@2.21.1 -- --no-auto-update
Sfor some reason
wrangler deploy
KAre you sure you're in the right directory?
Sfixed
Sforgot it was
bun run deploy
Hanyone having a solution for this ?
VHeyo. @Wrangler office hours will start August 5, 2024 https://discord.gg/cloudflaredev?event=1257618132206620702
Shello, here did someone got to work VSCode Debugger and Wrangler ?
I have searched in the diff channel and it seems 3-4 persons have the same issue (me included).
The first breakpoint is hit, but it's just loading, cannot skip etc.
any clue, hint to debug that?
I have searched in the diff channel and it seems 3-4 persons have the same issue (me included).
The first breakpoint is hit, but it's just loading, cannot skip etc.
any clue, hint to debug that?
!Hello, developers
I got error when I run the vite project on local.
The problem is this.
I got error when I run the vite project on local.
The problem is this.
!Please help me. thanks
!
wrangler 3.32.0 (update available 3.68.0)-------------------------------------------------------
[wrangler:inf] Ready on http://127.0.0.1:8788
⎔ Starting local server...
Parsed 2 valid header rules.
[wrangler-UserWorker:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2
024-03-04",
but you've requested "2024-08-05". Falling back to "2024-03-04"...
Features enabled by your requested compatibility date may not be available.
Upgrade to
wrangler@3.68.0X [ERROR] service core:user:worker: Uncaught ReferenceError: process is not defined
at null.<anonymous> (dwdwibrtjo.js:182105:20) in
../node_modules/next/dist/client/has-base-path.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:182132:24) in
../node_modules/next/dist/shared/lib/router/utils/is-local-url.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:182861:23) in
../node_modules/next/dist/client/resolve-href.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:183532:24) in ../node_modules/next/dist/client/link.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:183916:23) in ../node_modules/next/link.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in __require22
X [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional
logging output above.
BI like wrangler 
1DNS over Discord: GitHub
View the DNS over Discord source code on GitHub at https://dns-over-discord.v4.wtf/github
MHey there!
I was wondering if this issue with Durable Objects from CF Pages within
I'm gonna need it in the near future and I'm trying to estimate the overall effort of my project if this feature gets implemented soon.
I was wondering if this issue with Durable Objects from CF Pages within
wrangler devI'm gonna need it in the near future and I'm trying to estimate the overall effort of my project if this feature gets implemented soon.
GitHub
Describe the solution When binding a durable object using RPC that was defined in a different worker, it fails with: Cannot access
MyDurableObject#myMethod
CDon't expect it anytime soon (this month, for example), as I haven't even heard rumours of it being a thing "soon".
CAlso, considering the problem I'm having with not even being able to bind the DO (which I've already opened a ticket)... (see the last GH comment on that issue).
HWe are merging Pages into Workers soon, if that is what you mean?
CWell that passed below the radar for me I guess. But that's super exciting news.
So I guess we'll have to reassess the current issues after that merge.
Is there an ETA (even if just a rough figure/ballpark)?
So I guess we'll have to reassess the current issues after that merge.
Is there an ETA (even if just a rough figure/ballpark)?
HGitHub
What this PR solves / how to test
This PR changes the copy for assets and legacy-assets flags & config keys from We are going to be changing its behavior on August 15th. to We are going to ...
This PR changes the copy for assets and legacy-assets flags & config keys from We are going to be changing its behavior on August 15th. to We are going to ...
CYea I haven't even figured out what the 'assets' even are/represent, so...
I guess that isn't all that great news then.
I guess that isn't all that great news then.
HBasically the
env.ASSETSAh, that's for grabbing static stuff from within the Workers/Functions, right? (like a static image that's on the front-end code, or a static JSON data file, for ex.)
That's cool I guess, but unfortunately for me it isn't the problem I'm having
That's cool I guess, but unfortunately for me it isn't the problem I'm having
IWhy does
wrangler tail
OExperienced the same. If I have worker A calling worker B, B needs to start before A. This makes it a bit complicated in a monorepo setup with a single dev command starting all workers as separate packages, but https://github.com/vercel/turbo/issues/1497#issuecomment-1424852247 gave me a workaround
GitHub
Describe the feature you'd like to request In our monorepo, we have multiple services that to some degree depend on each other. For local development, we have to start a mock service first, the...
WThat if i understand correctly will just make kv-assets-handler that is part of worker sites unnecessary. If each worker has 'assets' associated, then you can just use that like on CF-Pages (that already has the assets binding on functions). That means that features like Gradual deployments will just work. Today you cant use Gradual deployments with worker sites because KV is always pointing to the last version.
Its just a part of the 2023 merge for worker+pages: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience
Its just a part of the 2023 merge for worker+pages: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience
The Cloudflare Blog
Today we’re excited to announce that over the next year we will be working to bring together the best traits and attributes you know and love from each product into one powerful platform!
WBTW, I'm still using Worker Sites today. Way more convenient to me, but I'm looking forward to that merge happens to avoid pay for static assets distribution like on we have on Pages, and stop with the pollution my logs with assets requests. Couple assets with a specific worker deployment will make a huge difference for me, the "rollback" will actually work as intended.
CReading that blog post...
It seems like this merge is more about giving Workers the 'abilities' of Pages (and unifying the Dashboard front-end) than giving Pages Functions all the Worker capabilities (which is what I was hoping for).
It seems like this merge is more about giving Workers the 'abilities' of Pages (and unifying the Dashboard front-end) than giving Pages Functions all the Worker capabilities (which is what I was hoping for).
HYeah, the end goal is to get rid of Pages entirely
HAnd just make it all a single product(Workers)
DThis would be amazing, looking forward to it! I‘m also using worker sites because of the better integration workers have. But I love the preview builds, envs and rollbacks pages provides
MHi. I'm addressing the same issue as this
https://github.com/cloudflare/workers-sdk/issues/4375
I'm thinking of using
Are there any ways to pass config to
https://github.com/cloudflare/workers-sdk/issues/4375
I'm thinking of using
Miniflareunstable_devMiniflareAre there any ways to pass config to
MiniflareGitHub
Describe the solution I used the package, msw to mock some external URLs, but if you use the unstable_dev then external call are still made and they aren't interceptors. Is there anyway this co...
MThank you, but I don't use it because it can't be used with another environment like this
https://github.com/dextertanyj/vitest-environment-testcontainers
https://github.com/dextertanyj/vitest-environment-testcontainers
GitHub
A Vitest environment with integrated support for Testcontainers. - dextertanyj/vitest-environment-testcontainers
II figure I'll post this here one more time in case anyone wants the StackOverflow bounty https://stackoverflow.com/questions/78831955/how-to-remove-wrangler-from-a-cloudflare-pages-project
Stack Overflow
I have a Cloudflare Pages project that uses Wrangler to run a function locally. I've recently Dockerized the project and since the function uses Hono, I can run that locally using a Node container,...
JLooks like you are trying to use Node style process.env in worker code. Refer here to use Env variables in your code. https://developers.cloudflare.com/workers/configuration/environment-variables/
Cloudflare Docs
Attach text strings and JSON values as environment variables to your Worker.
!thanks your support
Ehello everyone! I was wondering if any of you has managed to find a way to colorize json when we are using wrangler tail. Just to know... I log into json objects and was wondering if there was a nice way to see the output in diferent colors. Sorry for the double post also in the workers thread.
JWhat is the best strategy to deploy multiple workers or a combination of workers and pages as a single deployable unit? My initial thought is to use a monorepo with multiple steps, but perhaps there is a more native approach.
DI use a monorepo and lerna
AI don't suppose there's a way to get wrangler to execute a file such that at any entrypoint I can get access to the env values - even if that means it just calls fetch() as part of the script entrypoint? as a hack I could just call the script via http, but was looking for something a bit more native?
HWhat are you trying to do? Dump the environment variables? Interact with with bindings? Something else?
AHave an initial script that processes some data and pushes it it to a D1 DB - so I want the context of a DB etc in the normal way it might be used in a worker, so I can use shared code.
I currently have a /setup route that does some initial config for the worker - but I'd rather it were run as a script and not make it accessible to be called through the worker.
I currently have a /setup route that does some initial config for the worker - but I'd rather it were run as a script and not make it accessible to be called through the worker.