Don't expect it anytime soon (this month, for example), as I haven't even heard rumours of it being
Don'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.ASSETS binding in Functions, but for Workers(at least how I understand it)CAh, 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 typically take a long time to flush logs for a worker/DO?
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
Miniflare instead of unstable_dev, but Miniflare doesn't load wrangler.toml automatically, right?Are there any ways to pass config to
Miniflare easily?GitHub
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.
HYeah, I don't think there is anything that can do that atm
HYou could make an RPC Entrypoint(which by definition cannot be called externally), but that just kicks the ball down the road, as you would still need a different Worker to actually call the RPC Entrypoint
AI suppose as a hacky way around it I could also have a call that literally has itself look up its own environment variable options (eg, port) and call itself, then exit.
ぴis there a way to generate a presigned URL in wrangler for local R2?
scenario:
scenario:
- I store an object with
wrangler r2 object put <OBJECT_PATH> --local --file <MY_FILE - from my local environment, I want to generate a presigned URL for the locally stored images
Enot in wrangler, i would use aws cli or rclone for this
HNote, this doesn't work against a local R2 store
ぴcool, thanks guys! guess I will work some way out to use the production bucket
.Is there a vscode extension or similar that gives syntax highlight (I think it’s called) and other stuff to the wrangler.toml file?
MI'm trying to deploy a worker that builds fine with an external dependency called
Activating node compat flags in both ways just return different errors, I opened an issue on GH for more info: https://github.com/101arrowz/fflate/issues/220 but I'm not sure if this is something that depends on them or on me.
Any idea?
fflate but if I try to push it to Cloudflare through wrangler it complains about import { createRequire } from "module" that the dependency compiled code has.Activating node compat flags in both ways just return different errors, I opened an issue on GH for more info: https://github.com/101arrowz/fflate/issues/220 but I'm not sure if this is something that depends on them or on me.
Any idea?
HI use
Even Better TOMLExtension for Visual Studio Code - Fully-featured TOML support
.Thank you 
HOr
wrangler.json when I can get away with it
MAlready tried that but didn't work, now I just solved it by solving another problem
I had a custom esbuild command for wrangler that I set a long time ago for some integration reason, by using the
Thanks for the prompt help!
I had a custom esbuild command for wrangler that I set a long time ago for some integration reason, by using the
wrangler deploy --dry-run --outdir=path/to/build for the build, the deploy went well, and the library is working like a charm!Thanks for the prompt help!
IPlease do not crosspost your questions. You were already warned once.
AHey All - I was working today on a Worker that listens to a Event Notification on a "put" of a file to R2. I sank some time in trying to figure out why uploading a file did not trigger my queue. After some time I realised that all was working as it should. Seems like R2 triggers don't work locally (while developing)
- I can confirm that they do work when deployed. Is this a know limitation? Or did I miss something obvious in the docs?
LIs there a way
wrangler pages dev [dist] can proxy the static asset that hosted by vite?Lwhy
--proxy The port to proxy (where the static assets are served) [deprecated] [number] and command The proxy command to run [deprecated] [string]Ldeprecated
H@Hard@Work | R2
Oare there plans to support sharing resources such as r2 or d1 on local development? say i bind to the same d1 by ID so it would make sense if wrangler communicated to connect to the same sqlite database
LCloudflare Docs
A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions with Cloudflare resources like KV, Durable Objects, R2, and D1. You can set bindings for both production and preview environments.
Oi have all of those in a wrangler.toml already from which it reads so thats fine
Oi mean when i have two separate workers bound to the same d1 instance, they should also be bound to the same sqlite instance locally
