hi all, im can use WasmJs from Kotlin in Wrangler? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

mani123

Mmani123 hi all, im can use WasmJs from Kotlin in Wrangler?

mani123

M

mani123OP•11/29/24, 5:50 PM

https://github.com/bashor/kotlin-worker-hello-world/tree/master

GitHub

GitHub - bashor/kotlin-worker-hello-world

Contribute to bashor/kotlin-worker-hello-world development by creating an account on GitHub.

neoney

N

neoney•11/29/24, 10:03 PM

im running

wrangler dev

wrangler dev

on a worker and I can't access the bindings made from anotehr worker

neoney

N

neoney•11/29/24, 10:03 PM

http://localhost:6284/workers

neoney

N

neoney•11/29/24, 10:03 PM

is unable to connect

neoney

N

neoney•11/29/24, 10:05 PM

neoney

N

neoney•11/29/24, 10:14 PM

now i get this

neoney

N

neoney•11/29/24, 10:15 PM

its supposed to be a http binding

neoney

N

neoney•11/29/24, 10:16 PM

ok i fixed it, turns out if you log the binding it errors but it works fine

Constantin

C

Constantin•11/30/24, 12:05 PM

any ideea how build variables like CF_PAGES_COMMIT_SHACF_PAGES_COMMIT_SHA and CF_PAGES_BRANCHCF_PAGES_BRANCH can be extracted in the qwik framework?

having them like:

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

is not working

Constantin

C

Constantin•11/30/24, 1:46 PM

does CF_PAGES_COMMIT_SHA and CF_PAGES_BRANCH are missing from workers ? (i'm using the new git integration)

Walshy

W

Walshy•11/30/24, 4:27 PM

no, the id is not private

Walshy

W

Walshy•11/30/24, 4:28 PM

it means nothing to anyone else, it cannot be used by anyone else

Walshy

W

Walshy•11/30/24, 4:28 PM

the whole of wrangler.toml is safe to share wherever

Walshy

W

Walshy•11/30/24, 4:28 PM

?pings also

SuperHelpflare

S

SuperHelpflare•11/30/24, 4:28 PM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

Walshy

WWalshy the whole of wrangler.toml is safe to share wherever

敖律风

敖

敖律风•12/1/24, 4:01 AM

thankyou~

jokester

J

jokester•12/1/24, 3:11 PM

I'm trying to understand how

wrangler dev

wrangler dev

uses chrome dev tools to inspect worker requests. But I can't see the picture yet.

The code suggests it uses a patched build of chrome-devtoolschrome-devtools . But I can't locate how wrangler starts chrome and talk to it.

Does anyone happen to have a hint? Thanks for any help:love:

jokester

J

jokester•12/1/24, 3:20 PM

Thanks I got that name too

jokester

J

jokester•12/1/24, 3:21 PM

I may found an entrypoint.
https://github.com/cloudflare/workers-sdk/blob/ff8f5ae03cd4a71bf7b468fcf3cd28bf064059ab/packages/wrangler/src/dev/hotkeys.ts#L4 This seems to be the "d" hotkey handler.

GitHub

workers-sdk/packages/wrangler/src/dev/hotkeys.ts at ff8f5ae03cd4a71...

Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk

jokester

J

jokester•12/1/24, 3:25 PM

Then in openInspector()openInspector() it just opens an webpage at https://devtools.devprod.cloudflare.dev/js_apphttps://devtools.devprod.cloudflare.dev/js_app
I don't understand how the page could communicate with a local process orz

Walshy

W

Walshy•12/1/24, 4:29 PM

https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/src/dev/inspect.ts#L254
https://github.com/cloudflare/workers-sdk/blob/ff8f5ae03cd4a71bf7b468fcf3cd28bf064059ab/packages/wrangler/templates/startDevWorker/InspectorProxyWorker.ts#L475-L611

jokester

J

jokester•12/1/24, 4:53 PM

wow I couldn't find that
So js_appjs_app page is but a webpage built on devtools code. It just talk to local WS in devtools protocol.
This is insanely cool thanks

oof2win2

O

oof2win2•12/1/24, 7:53 PM

i've been using wrangler dev for a while. just today i started getting errors like Failed to establish a new connection: [Errno 61] Connection refusedFailed to establish a new connection: [Errno 61] Connection refused (when trying to connect to :8787 via fetch). this has never happened to me before. is there any solution to this?

oof2win2

O

oof2win2•12/1/24, 8:38 PM

like i spin up wrangler, GET requests work, then i send in a POST and it breaks - wrangler doesn't log anything anymore and it is unresponsive - i can't even exit, i need to kill it

oof2win2

O

oof2win2•12/1/24, 8:39 PM

and this is the code i have setup - there's no way it should break

export default {
  async fetch(req, env) {
    if (req.method !== "POST")
      return Response.json({ message: "Method Not Allowed" }, { status: 405 });
    return Response.json({ status: "OK" }, { status: 200 });
  }
}

export default {
  async fetch(req, env) {
    if (req.method !== "POST")
      return Response.json({ message: "Method Not Allowed" }, { status: 405 });
    return Response.json({ status: "OK" }, { status: 200 });
  }
}

amlcodes

A

amlcodes•12/2/24, 5:44 AM

is there a way i can test my api and cf services /bindings in development without having to rely on a completely remote environment? I need to test my trpc hono worker using the r2 binding to hit the actual r2 store, not local. --remote causes my localhost cors to not work, and apparently chrome doesnt allow you to visit any page with HSTS instead of HTTPS which is what ngrok will give you on a subdomain, so i can't test with ngrok from a subdomain

kue

K

kue•12/3/24, 1:12 PM

Is there anyone here who experienced missing entry-point error when using cloudflare/wrangler-action@v3cloudflare/wrangler-action@v3?

Here are my workflows config that I inherit from the documentation:

name: Deploy staging

on:
  push:
    branches:
      - main

jobs:
  cloudflare:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        with:
          version: 8

      - name: Deploy to Cloudflare Pages
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          packageManager: pnpm

name: Deploy staging

on:
  push:
    branches:
      - main

jobs:
  cloudflare:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        with:
          version: 8

      - name: Deploy to Cloudflare Pages
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          packageManager: pnpm

The weird things is, when I specifcy the full command pages deploy PATH --project-name=kaget --branch=mainpages deploy PATH --project-name=kaget --branch=main the result has duplicate project name which leads to error no such file or directory

Walshy

W

Walshy•12/3/24, 1:23 PM

You do want pages deploy <path>pages deploy <path> as the command but you don't seem to be building the site in the Action which is why the distdist folder seems missing

Walshy

WWalshy You do want `pages deploy <path>` as the command but you don't seem to be buildi...

kue

K

kue•12/3/24, 1:44 PM

Ahh my bad, thank you for catching that. I think I need a break haha

flyingshoes

F

flyingshoes•12/3/24, 4:15 PM

Anyone seeing an increased error rate of Rate limited. Please wait and consider throttling your request speed [code: 10000]Rate limited. Please wait and consider throttling your request speed [code: 10000] ? We started seeing increased instances of this.

flyingshoes

F

flyingshoes•12/3/24, 4:19 PM

is the rate limiting applied on an account level? We are working on an enterprise level, so there are multiple teams developing under this account.

Original message was deleted

flyingshoes

F

flyingshoes•12/3/24, 7:58 PM

cool -- sent out a support ticket.

Original message was deleted

flyingshoes

F

flyingshoes•12/3/24, 9:11 PM

question -- I got it increased, but it was for my user. I'm a bit confused though. We are running wranger deploywranger deploy in CI (gh actions), so I don't think there's reference to my username in that environment. Or am I missing osmething?

Walshy

W

Walshy•12/3/24, 9:13 PM

You're right to be confused, it is confusing (sorry) - rate limits are per-user not per-account. So your user (the one you sign in with) is what was rate limited.
It's the same way API tokens were per-user until we recently introduced account level ones.

flyingshoes

F

flyingshoes•12/3/24, 9:15 PM

so would all of my teammates need to have their limits adjusted too then?

flyingshoes

F

flyingshoes•12/3/24, 9:17 PM

and to lastly confirm, so if a job failed for me, it could pass for my teammate if they were to re-run it on their side as their user isn't rate limited?

Walshy

W

Walshy•12/3/24, 9:54 PM

^ correct yeah. Whoever generated the API token, they will need that increased - alternatively, if it's an account owned one, i'm not fully sure the process but csup can advice

flyingshoes

F

flyingshoes•12/3/24, 10:00 PM

got it... okay, I reached out to support about if there's an account one (Cloudflare - 01297743 ticket) that we need to update. I'll see what they say. thank you both!

Ephemeros

E

Ephemeros•12/3/24, 10:56 PM

I found out that when wrangler 3.88 got released and made experimental-registry true, it broke something in my project, when I flip experimental-registry to be false manually it gets fixed

but.. what does that flag really do? what does it change?

If I have it false and I want it to be working in my a react router app with cloudflareDevProxy for vite, I can access the durable object namespaces, and when I don't have it false, it stops working (ExampleDO undefined[wrangler] Couldn't find

wrangler dev

wrangler dev

session for class "ExampleDO" to proxy to)

so... I'm guessing for me to not need that flag to be false, I'll need to fix something else somewhere?

Ephemeros

E

Ephemeros•12/4/24, 6:44 AM

Ah, cool, thanks!

Ephemeros

E

Ephemeros•12/4/24, 7:14 AM

hmm... I still have the same issue with 3.92.0 unfortunately :/

Ephemeros

E

Ephemeros•12/4/24, 7:32 AM

edit: resolved, my bad!

Hzao

H

Hzao•12/4/24, 2:30 PM

Is the doc site down? Trying to look up some wrangler command in the docs, but seems the whole Cloudflare developer docs site is down, and it’s not on the status page

Original message was deleted

Hzao

H

Hzao•12/4/24, 2:39 PM

Thx. It’s added just after my post

Original message was deleted

Hzao

H

Hzao•12/4/24, 2:39 PM

Yes it is. Cheers~

miljussss

M

miljussss•12/4/24, 11:49 PM

Hello? Is this familiar to some of you?

✘ [ERROR] service core:user:worker: Uncaught SyntaxError: Identifier '__cf_cjs' has already been declared

at null.<anonymous> (functionsWorker-0.36329744004126696.js:992)

miljussss

M

miljussss•12/4/24, 11:54 PM

happens when i run "npx wrangler pages dev dist" in a cloudflare pages project

James

J

James•12/5/24, 1:48 AM

What wrangler version are you using? I believe that was an issue with older versions

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export default {
  async fetch(req, env) {
    if (req.method !== "POST")
      return Response.json({ message: "Method Not Allowed" }, { status: 405 });
    return Response.json({ status: "OK" }, { status: 200 });
  }
}

export default {
  async fetch(req, env) {
    if (req.method !== "POST")
      return Response.json({ message: "Method Not Allowed" }, { status: 405 });
    return Response.json({ status: "OK" }, { status: 200 });
  }
}

name: Deploy staging

on:
  push:
    branches:
      - main

jobs:
  cloudflare:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        with:
          version: 8

      - name: Deploy to Cloudflare Pages
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          packageManager: pnpm

name: Deploy staging

on:
  push:
    branches:
      - main

jobs:
  cloudflare:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        with:
          version: 8

      - name: Deploy to Cloudflare Pages
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          packageManager: pnpm