Looks like `--x-json-config` but yeah, toml will work too

D

darkpool•2/20/25, 11:57 PM

one thing I'm a bit confused on how the version works. like just to confirm this is what wrangler should be in package.json? I honestly didn't know you could have a name for versioning haha

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

    "devDependencies": {
        "@cloudflare/vitest-pool-workers": "^0.6.4",
        "vitest": "~2.1.9",
        "wrangler": "dispatch-namespaces-dev"
    }

WWalshy Looks like `--x-json-config` but yeah, toml will work too

D

darkpool•2/21/25, 12:44 AM

Fixed previous issue with toml but now running into this ;/

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

[wrangler] Couldn't find `wrangler dev` session for "customer-worker-1" in namespace "my-namespace" to proxy to%

EDIT: got it to work finally. I kept getting spammed "Failed to get worker definitions TypeError: fetch" but after restarting machine erorr went away which fixed the above error. I'm using turbo repo with 6 workers and I there is a lot of problems with port collisions. I was specifying inspector_ports but just restarting machine seems to work.

Cchristianklotz I followed [the guide](https://developers.cloudflare.com/cloudflare-for-platform...

D

darkpool•2/21/25, 12:45 AM

Hi @christianklotz did you figure this out?

I

Ian Schenck•2/21/25, 1:46 AM

Are service bindings inside a namespace, among services in that namespace, possible? I'm getting errors from the API saying the script doesn't exist.

IIan Schenck Are service bindings inside a namespace, among services in that namespace, possi...

P

Payello•2/21/25, 12:58 PM

Service bindings are for your regular workers only. You must use a dispatch binding to access workers in namespaces.

D

Drew•2/24/25, 7:23 PM

I setup a simple worker and api call to add a hostname and setup ssl. Got the message about contacting for enterprise. Wondering if workers for platforms will let me make that call without going through the full process and getting the message. Any upfront advice welcome!

DDrew I setup a simple worker and api call to add a hostname and setup ssl. Got the m...

D

Drew•2/24/25, 7:27 PM

Nevermind

I found it!

D

darkpool•2/27/25, 1:17 AM

how do we access the args object from dispatcher in a user worker? I am trying it locallly following the guide but cant figure it out.
From the types

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

(method) DispatchNamespace.get(name: string, args?: {
    [key: string]: any;
}, options?: DynamicDispatchOptions): Fetcher
@param name — Name of the Worker script.


@param args — Arguments to Worker script.

@param options — Options for Dynamic Dispatch invocation.

@returns — A Fetcher object that allows you to send requests to the Worker script.

@throws — If the Worker script does not exist in this dispatch namespace, an error will be thrown.

I want to be able to do something like:

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

    .get("/", async (c) => {
        const customerScript = c.env.DISPATCHER.get("user-worker-dev", {
            hook: "afterCreate",
            table: "order",
        });
        return await customerScript.fetch(c.req.raw);

EDIT: looks like args is not implemented yet so going to try RPC.

DDmitry this worked!! ```ts import { WorkerEntrypoint } from 'cloudflare:workers' expor...

D

darkpool•2/27/25, 3:09 PM

Hi @Dmitry I did you get this working locally? I keep getting error: "worker.sum is not a function"

T

TDat•3/5/25, 10:52 AM

Hi, when uploading static assets with a normal worker, after deploying the worker, I'm automatically directed to the uploaded index.html file with js and css. However, if I deploy a platform worker and route to it with a dispatch worker, I can't get the app to be displayed. Is there any way serve files from platform worker to dispatch worker?

W

WalshyOP•3/5/25, 10:59 AM

Can you provide more info? It'll work the same way

T

TDat•3/5/25, 11:41 AM

@Walshy | Workers/Pages thanks for the response but I figured it out. I accidently passed the wrong subdomain.

S

Silvan•3/5/25, 12:37 PM

I honestly have a hard time understanding all use cases for platforms

lets say i sell unique websites to customers while also owning the domain. does this product still make sense? because so far normal workers can do the things i need

SSilvan I honestly have a hard time understanding all use cases for platforms lets say ...

A

Acе•3/5/25, 2:10 PM

No, that wouldn’t make sense for workers for platforms. It is more for giving the users of your website the ability to create their own workers, that usually extends the functionality of your website/app. For example, Shopify can use it to enable developers to create plugins for the checkout page, such as collecting additional information related to an order (e.g. a loyalty card number).

E

EinsiTang•3/7/25, 9:41 AM

hello , have someone here , I have same question about worker dev , fetch request always pending and I have no idea to fix it

E

EinsiTang•3/7/25, 9:53 AM

I can provide the warehouse and demonstration code to describe the problem. Is there anyone available to help me with code review?

D

Dagy•3/7/25, 9:06 PM

Hello community,

I’m trying to deploy a nuxt site to cloudflare. I used the nuxt starter from the cli.

But I haven’t been able to use the workers for the /server/api together with the hono library.
I get internal server error. And not functionality for the server/api

I haven’t this in my nuxt.config
export default defineNuxtConfig({
compatibilityDate: "2024-11-01",
devtools: { enabled: true },

nitro: {
preset: "cloudflare-module", // ← Correct preset here
},

modules: ["nitro-cloudflare-dev"],
vite: {
optimizeDeps: {
include: ["hono"],
},
},
});

I have this in my wrangler

{
"$schema": "node_modules/wrangler/config-schema.json",
"name": "test-1",
"compatibility_date": "2025-03-03",
"compatibility_flags": ["nodejs_compat"], // ← Required
"main": "./.output/server/index.mjs",
"assets": {
"binding": "ASSETS",
"directory": "./.output/public/"
},
"r2_buckets": [{ "binding": "BUCKET", "bucket_name": "your-bucket-name" }],
"kv_namespaces": [{ "binding": "KV", "id": "your-kv-id" }],
"d1_databases": [
{
"binding": "DB",
"database_name": "your-db-name",
"database_id": "your-db-id"
}
],
"ai": { "binding": "AI" },
"observability": { "enabled": true }
}

This my workers code:

// server/api/workers.js
import { Hono } from "hono";

const app = new Hono();

app.get("/", (c) => {
const name = c.req.query("name") || "World";
return c.json({ greeting:

Hello, ${name}!

Hello, ${name}!

Hello, ${name}!

Hello, ${name}! });
});

export default app;

R

rob•3/9/25, 1:34 PM

Pages or workers ?

C

cosbgn•3/9/25, 5:04 PM

Does worker for platform supports cron triggers?

T

thomasjiangcy•3/10/25, 3:45 PM

is there anyway to query bandwidth usage on a worker level within a dispatch namespace? e.g. want to charge for bandwidth as part of pricing

W

WalshyOP•3/10/25, 4:25 PM

Workers has no concept of bandwidth usage so no, not through our side

W

WalshyOP•3/10/25, 4:25 PM

though actually...

W

WalshyOP•3/10/25, 4:26 PM

you could sum { responseBodySize } in graphql, looks like we have responseBodySize in subrequests dataset too. don't think we have ingress but there's some data you could start to use

T

thomasjiangcy•3/10/25, 4:35 PM

got it, thanks!

WWalshy Looks like `--x-json-config` but yeah, toml will work too

D

darkpool•3/10/25, 4:44 PM

Hi Walshy im trying to find info on this but dont see it anywhere in docs? https://developers.cloudflare.com/search/?query=--x-json-config

W

WalshyOP•3/10/25, 4:45 PM

json config is now default, it doesn't need the flag anymore

WWalshy json config is now default, it doesn't need the flag anymore

D

darkpool•3/10/25, 4:49 PM

even for dispatch-namespaces-dev branch?

W

WalshyOP•3/10/25, 4:54 PM

oh no, you'd need the flag there (if it's supported i'm not 100% sure)

W

WalshyOP•3/10/25, 4:54 PM

but there's not really much info other than it allows wrangler.json

D

darkpool•3/10/25, 4:56 PM

ok thanks just to make sure im not using flag wrong it would be like this:

npx wrangler@dispatch-namespaces-dev dev --x-json-config

npx wrangler@dispatch-namespaces-dev dev --x-json-config

npx wrangler@dispatch-namespaces-dev dev --x-json-config

npx wrangler@dispatch-namespaces-dev dev --x-json-config correct?

W

WalshyOP•3/10/25, 6:26 PM

yep

P

preston•3/10/25, 9:23 PM

Hi, just trying to follow the Workers for Platforms example but having trouble getting dispatch_namespaces to work. in my wrangler.jsonc:

"vars": {
  "MY_VARIABLE": "production_value",
},

"dispatch_namespaces": [
  {
    "binding": "DISPATCHER",
    "namespace": "<NAMESPACE_NAME>",
  },
],

"vars": {
  "MY_VARIABLE": "production_value",
},

"dispatch_namespaces": [
  {
    "binding": "DISPATCHER",
    "namespace": "<NAMESPACE_NAME>",
  },
],

"vars": {
  "MY_VARIABLE": "production_value",
},

"dispatch_namespaces": [
  {
    "binding": "DISPATCHER",
    "namespace": "<NAMESPACE_NAME>",
  },
],

"vars": {
  "MY_VARIABLE": "production_value",
},

"dispatch_namespaces": [
  {
    "binding": "DISPATCHER",
    "namespace": "<NAMESPACE_NAME>",
  },
],

But when i run wrangler dev with:

export default {
  async fetch(req, env) {
    console.log('env:', Object.keys(env));

export default {
  async fetch(req, env) {
    console.log('env:', Object.keys(env));

export default {
  async fetch(req, env) {
    console.log('env:', Object.keys(env));

export default {
  async fetch(req, env) {
    console.log('env:', Object.keys(env));

I see logged:

env: [ 'MY_VARIABLE' ]

env: [ 'MY_VARIABLE' ]

env: [ 'MY_VARIABLE' ]

env: [ 'MY_VARIABLE' ]

Why do does

"vars"

"vars"

"vars"

"vars" modify env but

"dispatch_namespaces"

"dispatch_namespaces"

"dispatch_namespaces"

"dispatch_namespaces" doesn't?

Ppreston Hi, just trying to follow the Workers for Platforms example but having trouble g...

P

preston•3/10/25, 9:46 PM

Apparently the answer is that

"dispatch_namespaces"

"dispatch_namespaces"

"dispatch_namespaces"

"dispatch_namespaces" doesn't work in local dev mode right now, because I tried deploying and env does have a DISPATCHER key in prod. Is that a bug? The output from

wrangler dev

wrangler dev

wrangler dev

wrangler dev implies that it is working:

Your worker has access to the following bindings:
- Vars:
  - MY_VARIABLE: "production_value"
- Dispatch Namespaces:
  - DISPATCHER: <NAMESPACE_NAME> [connected to remote resource]
⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:8787

Your worker has access to the following bindings:
- Vars:
  - MY_VARIABLE: "production_value"
- Dispatch Namespaces:
  - DISPATCHER: <NAMESPACE_NAME> [connected to remote resource]
⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:8787

Your worker has access to the following bindings:
- Vars:
  - MY_VARIABLE: "production_value"
- Dispatch Namespaces:
  - DISPATCHER: <NAMESPACE_NAME> [connected to remote resource]
⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:8787

Your worker has access to the following bindings:
- Vars:
  - MY_VARIABLE: "production_value"
- Dispatch Namespaces:
  - DISPATCHER: <NAMESPACE_NAME> [connected to remote resource]
⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:8787

L

lusons•3/11/25, 3:01 PM

Can I use the restful api to upload worker assets in compressed format?

W

WalshyOP•3/11/25, 3:16 PM

You cannot upload a compressed Worker bundle today, what compression were you looking to use and why?

WWalshy You cannot upload a compressed Worker bundle today, what compression were you lo...

L

lusons•3/11/25, 3:28 PM

Thanks for your reply, I'm not sure if my idea is correct. In my scenario, I want to deploy the html + otherAssets + userWorker.js produced by the saas service to a worker, and then distribute it by dispatcher (similar to the publishing function of framer.com), but currently I can only use base64 for network transmission, which will be very slow. Or do I have other ways?

W

WalshyOP•3/11/25, 3:29 PM

using Workers Assets yeah it'd be base64 but that shouldn't be slow unless you're uploading a lot of data, for almost all sites it should take almost no time at all. We recommend concurrent uploads of these asset buckets

N

nclevenger•3/11/25, 3:34 PM

can you deploy the Agent SDK on Workers for Platforms?

AAhmad Awais How do y’all complie, pkg, and bundle the code meant to be deployed via workers ...

N

nclevenger•3/12/25, 8:28 AM

You can use wrangler to deploy to WfP, but it's also fairly straightforward to run ESBuild even on workers, including even bundling dependencies from http url imports ... there's a simple example of this w/ API at https://esb.denoflare.dev for example

esbuild as an edge service

We run esbuild so you don't have to.

R

rob•3/12/25, 3:04 PM

are you letting you users build via. CLI tool or ?

R

rob•3/12/25, 3:04 PM

Or how are they pushng the code up to your platform

AAhmad Awais Yes we can use wrangler but how? It’s users code coming to us. So code isn’t ava...

I

Isaac McFadyen•3/12/25, 3:06 PM

Workers for Platforms isn't meant as a fully-packaged, batteries-included solution. The idea with WfP is you upload compiled Workers to the platform which are then run, it doesn't include CI/CD because that's not the goal of the platform, really.

I

Isaac McFadyen•3/12/25, 3:07 PM

The expectation is that customers bring their own build system.

AAhmad Awais What am I missing here? How can anyone use WfP today in the world of TypeScript ...

D

DaniFoldi•3/12/25, 4:11 PM

Very easy to use in my opinion. I also think that the "open" approach of WfP is great, I can "bring my own" way of building workers - and ours is pretty unconventional, we generate the API within another worker, in one case. In another, we use fly.io, it took no more than a day to set up esbuild bundling

Looks like `--x-json-config` but yeah, toml will work too

Similar Threads

Similar Threads

Similar Threads