I’d start in the contributing guide: <https://github.com/cloudflare/workers-sdk/blob/main/CONTRIBUTI

JJames I’d start in the contributing guide: <https://github.com/cloudflare/workers-sdk/...

R

Rubi•10/24/24, 2:51 PM

somehow, it's not beginner friendly enough, and I had to use private NPM registry to test the package I edit

Hhaeeeil hello, can i load the code deployed from the worker dashboard in wrangler?

J

JamesOP•10/24/24, 2:52 PM

Check out

init —from-dash

init —from-dash

init —from-dash

init —from-dash: https://developers.cloudflare.com/workers/wrangler/commands/#init

RRubi somehow, it's not beginner friendly enough, and I had to use private NPM registr...

J

JamesOP•10/24/24, 2:53 PM

If you can create an issue with specifically which steps during build and execute failed for you and how exactly they failed, I’m sure the team would love to improve the docs

C

Cayter•10/24/24, 3:49 PM

does anyone know if there's a ticket that tracks adding workerd support in vitejs powered apps via vitejs's environment api? or the work hasn't been started yet? thx

main use case is to have our remix app in local development mode being able to access r2/d1/ai/queue/etc. without relying on limited support like getPlatformProxy()

F

freddw•10/26/24, 8:23 PM

Has anybody run into the problem where no matter what workaround they try (eg those mentioned in https://github.com/cloudflare/workers-sdk/issues/2874#issuecomment-2439725814 and in the docs at https://developers.cloudflare.com/workers/wrangler/commands/#login) they cannot successfully login to wrangler on a headless machine? IMO, that github issue should be reopened since the problems with the headless login impl were never properly addressed, and none of those workarounds seem generalizable / stable

F

freddw•10/26/24, 8:26 PM

I added a little explanation at the end of my comment for what could be changed to implement headless logins like gcp's gcloud, which I've never had problems with. I'd go so far as to try to implement it myself if I could, but I think it necessitates coordinated serverside changes, because it doesn't seem possible to change redirect URLs away from localhost clientside

K

kian•10/27/24, 2:00 AM

I think most people just use API tokens

F

freddw•10/27/24, 8:54 PM

Let me try setting that up again, I tried a couple months ago (if by API tokens you mean

export CLOUDFLARE_API_TOKEN="API token generated from the Edit Workers (or equivalent) template"

export CLOUDFLARE_API_TOKEN="API token generated from the Edit Workers (or equivalent) template"

export CLOUDFLARE_API_TOKEN="API token generated from the Edit Workers (or equivalent) template"

export CLOUDFLARE_API_TOKEN="API token generated from the Edit Workers (or equivalent) template"

but I remember running into some issue where wrangler treated me as logged in in some cases and unauthenticated in others. To me that looked like an authn issue on wrangler's end rather than authz.

I started poking through wrangler's internal impl (IIRC the problem was that wrangler login set more login configs than just token so manually setting the token didn't work when those other configs were need). Then I checked out the cf HTTP apis to see if I could do it myself over curl, but then I discovered at least a couple things I wanted to do had no http API documentation / what did exist didn't have enough info to know what to pass as args without studying the wrangler impl too much. Tried anyway for a bit and then called it quits after a couple hours total

F

freddw•10/27/24, 8:57 PM

anyway it's possible it was user error on my side but if this is a typical user experience (trying to login and it failing with a weird error, having to track down the official docs at https://developers.cloudflare.com/workers/wrangler/commands/#login, realize they don't work, then track down https://github.com/cloudflare/workers-sdk/issues/2874 and try one or more things, then maybe have to track down the cf discord) I humbly request that it be treated as a bug even if "it's always been this way" or doesn't end up blocking most users

A

Alex•10/28/24, 11:08 AM

Is there a way to have

wrangler types

wrangler types

add the generic "body" type for a

Queue

Queue

Queue

Queue?

AAlex Is there a way to have `wrangler types` add the generic "body" type for a `Queue...

D

DaniFoldi•10/28/24, 11:59 AM

I don't think there is one today, but this would be a good feature request. Could you open an issue for it? https://github.com/cloudflare/workers-sdk/issues/new/choose

A

Alex•10/28/24, 12:31 PM

Yeah for sure, will do!
Done: https://github.com/cloudflare/workers-sdk/issues/7112

A

appu•10/29/24, 6:40 PM

guys quick question what are the flag parameters for wrangler to create a angular app without ssr.

A

alphem•10/31/24, 12:00 AM

Hey, I'm having trouble with wrangler and I don't know if it's me or not. I'm currently trying save a secret for the first time using

npx wranger secret put foo

npx wranger secret put foo

npx wranger secret put foo

npx wranger secret put foo. It opens up the cloudflare consent screen, but then when I click "allow", it hangs. Any thoughts?

M

MattIPv4•11/1/24, 6:39 PM

:Wave_Doggo: Is

--test-scheduled

--test-scheduled

--test-scheduled

--test-scheduled working for folks in the latest version of Wrangler?

M

MattIPv4•11/1/24, 7:11 PM

It would seem 'tis broken, filed https://github.com/cloudflare/workers-sdk/issues/7152

GitHub

🐛 BUG: `--test-scheduled` w/ custom build does not work from 3.80.0...

Which Cloudflare product(s) does this pertain to? Wrangler What version(s) of the tool(s) are you using? 3.80.0 What version of Node are you using? 20.9.0 What operating system and version are you ...

MMattIPv4 It would seem 'tis broken, filed https://github.com/cloudflare/workers-sdk/issue...

W

Walshy•11/1/24, 7:36 PM

out of interest does

--x-dev-env=false

--x-dev-env=false

--x-dev-env=false

--x-dev-env=false fix it?
(it shouldn't but i can't see any other changes that would haha)

WWalshy out of interest does `--x-dev-env=false` fix it? (it shouldn't but i can't see a...

M

MattIPv4•11/1/24, 8:33 PM

Yessir, it does

W

Walshy•11/1/24, 8:36 PM

huh..

C

Curtis Doty•11/2/24, 8:59 PM

How to disable the spinner on the CLI?

C

Curtis Doty•11/2/24, 10:46 PM

Basic dev qeustion here. I've patched create-cloudflare to disable the spinner on git commit. This is needed to prevent corruping the gpg password prompt. However, even after I run

pnpm run build --filter create-cloudflare

pnpm run build --filter create-cloudflare

pnpm run build --filter create-cloudflare

pnpm run build --filter create-cloudflare then running

pnpm create cloudflare hello-world --type hello-world --ts --git

pnpm create cloudflare hello-world --type hello-world --ts --git

pnpm create cloudflare hello-world --type hello-world --ts --git

pnpm create cloudflare hello-world --type hello-world --ts --git doesn't appear to run my local code. What am I doing wrong?

T

TheKaiser•11/4/24, 5:13 AM

Anyone have advice on getting devtools to open on linux? I have chromium and chrom installed but when I press d I just get "Inspector depends on having a Chromium-based browser installed, maybe you need to install one?"

V

Vero•11/4/24, 4:21 PM

https://discord.gg/sD5JwVnE?event=1293141618353766411

V

Vero•11/4/24, 8:18 PM

Heyo. Here's the recording of the Wrangler Office Hours

Wrangler_Office_Hours_-_November_2024.mp323.14MB

T

Tarnadas•11/5/24, 10:36 AM

Hey, is it possible to connect to the logs when doing integration testing via

unstable_dev

unstable_dev

unstable_dev

unstable_dev?

T

Tarnadas•11/5/24, 10:38 AM

ah nvm found

logLevel

logLevel

logLevel

logLevel

F

funmiles.•11/5/24, 5:45 PM

With wrangler 3, is it possible to do development while using remote D1 database?

pnpm dev

pnpm dev

pnpm dev

pnpm dev uses the local database (which is fine most of the time). There is no

pnpm dev --remote

pnpm dev --remote

pnpm dev --remote

pnpm dev --remote like there was using

wrangler dev

wrangler dev

. Is there some way to make it work? Environment variable maybe?

T

topmass•11/8/24, 6:09 PM

ello friends, I've been getting stuck on deploying next with wrangler lately, generally any other framework starters work. I'm on windows and then fully installed a fresh new WSL2 and node and wrangler package and now have it almost there it seems but its getting stuck here:/

anyone know of a fix ?

T

topmass•11/8/24, 6:21 PM

i think non issue its working and deployed

T

topmass•11/8/24, 6:27 PM

just got stuck on that step it seems in wsl everything else working fine

B

Baby Beel•11/8/24, 11:10 PM

Do you know how to use worker to run mysql2 locally?
I wish I could do something like that:

export async function getDB(c: Bindings) {
  if (c.ENV == "development") {
    return new Kysely<Database>({
      dialect: new MysqlDialect({
        pool: createConnection ({
          host: c.DATABASE_HOST,
          database: c.DATABASE_DATABASE,
          user: c.DATABASE_USERNAME,
          password: c.DATABASE_PASSWORD,
        })
      })
    })
  } else {
    return new Kysely<Database>({
      dialect: new PlanetScaleDialect({
        username: c.DATABASE_USERNAME,
    password: c.DATABASE_PASSWORD,
    host: c.DATABASE_HOST
      })
    })
  } 
}

export async function getDB(c: Bindings) {
  if (c.ENV == "development") {
    return new Kysely<Database>({
      dialect: new MysqlDialect({
        pool: createConnection ({
          host: c.DATABASE_HOST,
          database: c.DATABASE_DATABASE,
          user: c.DATABASE_USERNAME,
          password: c.DATABASE_PASSWORD,
        })
      })
    })
  } else {
    return new Kysely<Database>({
      dialect: new PlanetScaleDialect({
        username: c.DATABASE_USERNAME,
    password: c.DATABASE_PASSWORD,
    host: c.DATABASE_HOST
      })
    })
  } 
}

export async function getDB(c: Bindings) {
  if (c.ENV == "development") {
    return new Kysely<Database>({
      dialect: new MysqlDialect({
        pool: createConnection ({
          host: c.DATABASE_HOST,
          database: c.DATABASE_DATABASE,
          user: c.DATABASE_USERNAME,
          password: c.DATABASE_PASSWORD,
        })
      })
    })
  } else {
    return new Kysely<Database>({
      dialect: new PlanetScaleDialect({
        username: c.DATABASE_USERNAME,
    password: c.DATABASE_PASSWORD,
    host: c.DATABASE_HOST
      })
    })
  } 
}

export async function getDB(c: Bindings) {
  if (c.ENV == "development") {
    return new Kysely<Database>({
      dialect: new MysqlDialect({
        pool: createConnection ({
          host: c.DATABASE_HOST,
          database: c.DATABASE_DATABASE,
          user: c.DATABASE_USERNAME,
          password: c.DATABASE_PASSWORD,
        })
      })
    })
  } else {
    return new Kysely<Database>({
      dialect: new PlanetScaleDialect({
        username: c.DATABASE_USERNAME,
    password: c.DATABASE_PASSWORD,
    host: c.DATABASE_HOST
      })
    })
  } 
}

<

<Alterion.Dev>•11/10/24, 4:52 AM

is there any way to get full errors displayed in wrangler? It's getting really tiresome to constantly need to add try/catch everywhere, otherwise the only log I get is

[wrangler:inf] GET /api/me 500 Internal Server Error (43ms)

[wrangler:inf] GET /api/me 500 Internal Server Error (43ms)

[wrangler:inf] GET /api/me 500 Internal Server Error (43ms)

[wrangler:inf] GET /api/me 500 Internal Server Error (43ms) which is entirely useless for any purpose whatsoever.

<

<Alterion.Dev>•11/10/24, 4:57 AM

How am I supposed to debug this >.<

<

<Alterion.Dev>•11/10/24, 5:07 AM

And before you say "check the /api/me" endpoint, that ain't it. The error was in the preflight for a custom middleware for itty-router and I had to dig reaaaaaaaal deep with console logs just to figure that out. It's wasting my time.

V

Victor Berchet•11/10/24, 8:03 AM

Can you try listening to the top level error event:

addEventListener('error', (e) => {
    console.log(e.error);
});

addEventListener('error', (e) => {
    console.log(e.error);
});

addEventListener('error', (e) => {
    console.log(e.error);
});

addEventListener('error', (e) => {
    console.log(e.error);
});

I

i.wont.tell•11/10/24, 10:39 AM

can we specify encrypted env vars when setting up wrangler.toml for pages functions? I only see in the docs a way to setup different env vars for production and development but there is nothing about encrypted env vars or maybe I'm missing it

I

i.wont.tell•11/10/24, 10:41 AM

ah, yes, secrets, sorry

I

i.wont.tell•11/10/24, 10:44 AM

I see that's for setting it up in Cloudflare, but how do I set it up for local development? Does wrangler downloads the secrets automatically when running

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev?

Original message was deleted

I

i.wont.tell•11/10/24, 10:51 AM

thank you! unless I'm blind it would be great to have that info on the pages docs

VVictor Berchet Can you try listening to the top level error event: ``` addEventListener('error'...

<

<Alterion.Dev>•11/10/24, 1:05 PM

That did work. Shouldn't there be some wrangler.toml option that makes this easy? Seriously this friction is pretty unnecessary.

VVictor Berchet Can you try listening to the top level error event: ``` addEventListener('error'...

<

<Alterion.Dev>•11/10/24, 1:25 PM

wait actually no that doesn't seem to catch all errors. some but somehow not all? I dunno man this is really annoying.

<

<Alterion.Dev>•11/10/24, 1:25 PM

The worst part of this is that the client gets the error.

{"status":500,"error":"Cannot read properties of undefined (reading 'join')"}

{"status":500,"error":"Cannot read properties of undefined (reading 'join')"}

{"status":500,"error":"Cannot read properties of undefined (reading 'join')"}

{"status":500,"error":"Cannot read properties of undefined (reading 'join')"}. Why would the client get the error but wrangler doesn't?

<

<Alterion.Dev>•11/10/24, 1:33 PM

Oh. That's... actually possible. it's itty-router. Let me double-check that.

MMattIPv4 Yessir, it does

J

jumpspace•11/10/24, 4:47 PM

I tried adding beside --test-scheduled but I am getting warning
[wrangler-UserWorker:wrn] Miniflare 3 does not currently trigger scheduled Workers automatically.
Use

--test-scheduled

--test-scheduled

--test-scheduled

--test-scheduled to forward fetch triggers.

with and without the --x-dev-env=false i am getting 404 error
. means the _scheduled route is still not accessibel

Jjumpspace I tried adding beside --test-scheduled but I am getting warning [wrangler-User...

M

MattIPv4•11/10/24, 4:52 PM

The latest release fixed it for me based on the repro I'd given them. If you're still seeing issues on the latest release, create a minimal repro and file an issue

Original message was deleted

J

jumpspace•11/10/24, 5:16 PM

no I am usign __scheduled

J

jumpspace•11/11/24, 1:05 AM

i created a new repo with cron job template. when making a request to the scheduled job the request never ends and keep processing while not running the scheduled job as well.

J

jumpspace•11/11/24, 11:58 AM

ok folks. I figured out the Solution.

I was creating a scheduled job in A honojs file. That means implementing a scheduled worker in a -

npm create hono@latest my-app

npm create hono@latest my-app

npm create hono@latest my-app

npm create hono@latest my-app repo
That was causing all sorts of issue.

Then I created a fresh repo with

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker then installed honojs to it and now the scheduled worker is working

N

naourass•11/16/24, 1:55 AM

Hi all, any idea what could cause this #miniflare error when trying to run a big insert query on a local D1 db through

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()?

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

I’d start in the contributing guide: <https://github.com/cloudflare/workers-sdk/blob/main/CONTRIBUTI

Similar Threads

Similar Threads

Similar Threads