How can I optimize the latency of workers when using D1 in free plan?
How can I optimize the latency of workers when using D1 in free plan?
Nits around 300-400ms on an avg with smart placement
Swanted to ask this about KV too, having similar issues and had to swap to durable objects just due to it being so slow
Nyeah confused with normal and smart placement
HI used both solidjs and nextjs with wrangler, but
wrangler dev
Snextjs works with most bindings
i use it with D1 just fine
i use it with D1 just fine
MAny example Kotlin/Wasm or Kotlin/Js ?
HNote this is #wrangler office hours, you might want to ask in #d1-database
Noh ok
Eis "python support?" valid as a question? :D
HI think you are correct that the D1 binding works in Nextjs. But I think the dev mode still is not actual dev mode right?
VWill Wrangler v4 have Wrangler <> live workers environments (same worker different environment like wrangler V1 vs technically separately workers)
BAre there any plans for extending functionality of
I'm currently doing my builds through vite, utilising terser, then pointing wrangler at the output JS.. just to keep full control over tree-shaking and minification. (Works out like 40% smaller in my use cases)
minifyI'm currently doing my builds through vite, utilising terser, then pointing wrangler at the output JS.. just to keep full control over tree-shaking and minification. (Works out like 40% smaller in my use cases)
D+1, and outputting sourcemaps and metafiles from esbuild would be nice
Syeah it's not; no
LWorkers are pages converging. Is pages merging into Workers or will there be a new entity, like projects or something?
DI am not sure if this is the right channle for this, but when I try to run Hono app integrated with wrangler on local, it says it's ready on http://127.0.0.1:8787
but when I send request, it's just loading and not sending back any response
can anybody please help me with this?
but when I send request, it's just loading and not sending back any response
can anybody please help me with this?
ZThe Astro integration, are you guys aware of it? Have you ever considered creating a plugin to "build" a project using cloudflare so we can see the compatibility ahead of time?
BWill take a look! Thanks.
Zoh neat, that sort of answers my question too I think? I have had a hard time with Cloudflare in the past, but it was because of
ulidthat's cool, thanks
Dnow we just need https://github.com/cloudflare/workers-sdk/issues/4633
VOh no, I meant like environments in wrangler file create whole new workers (even though they're technically the same but prod/dev) when pushed. In the wrangler v1 days, I remember it appearing as 1 worker when pushed, but with different environments.
Vadjacent question, does this work only for workers + static assets or for pages too?
Lgit ci/cd, gitops, automatic builds, build on cloud, on wrangler?
Dwould be nice if DO migrations were an inheritable but also overrideable at an env-level, since they're deployed as separate workers
Tany chance wrangler will support splitting files for deployment? the resulting
index.jsyay awesome! I wanted to ask too, does CF have any plans to support like, for instance, I wanted to support WASM FFMPEG locally, but I can't upload the full file to pages (32 MB) to allow users run it locally
Z
HYou could throw it into R2 and then serve it via a Worker? Though that is for the Assets team, not
wrangler
ACloudflare Docs
Set up continuous integration and continuous deployment for your Workers.
Da stable API would be nice, too
Zcopy. I was mostly wondering because I was putting it in my public folder
Lwill wrangler be published on jsr anytime soon?
Swill we get a bit more infos about the vite plugin? are all frameworks listed in worker assets supported?
like i currently use the worker assets template for sveltekit that already uses vite and i dont quite get what would change if i added that plugin. would it be like vite dev + wrangler dev?
like i currently use the worker assets template for sveltekit that already uses vite and i dont quite get what would change if i added that plugin. would it be like vite dev + wrangler dev?
Vin
i often get very confused by what's the direction going forward (is pages gonna get deprecated in favour of worker assets? no idea). same here. it would be nice if in the docs, or somewhere, there was even just a simple list that lists the things that will be used going forward, and what will be deprecated some time in the futer (aka: if you want, you can already start moving away from it if the replacement's downsides don't affect you)
@cloudflare/vite-pluginwrangler devi often get very confused by what's the direction going forward (is pages gonna get deprecated in favour of worker assets? no idea). same here. it would be nice if in the docs, or somewhere, there was even just a simple list that lists the things that will be used going forward, and what will be deprecated some time in the futer (aka: if you want, you can already start moving away from it if the replacement's downsides don't affect you)
SI had the same question before. they wont call pages deprecated yet but now that worker assets supports even more things that were “special” for pages its fairly clear to me that its the way going forward. pages just dosent integrate as nicely
Vi've had the same feeling, but not having a clear way to know all this aside from working at cf is kinda annoying :‘)
