out of interest does `--x-dev-env=false` fix it? (it shouldn't but i can't see any other changes tha

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

WalshyOP•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

then running

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

?

T

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

ah nvm found

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

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

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)

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);
});

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

?

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')"}

. 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

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

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

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()

?

/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

N

naourass•11/16/24, 2:06 AM

Here's the code, it works fine with small data, but throws the error above when the batch data is relatively big:

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

K

Kimitri•11/16/24, 9:26 AM

is safe expose ids from wrangler binds in an public repository? There's some way to pass this throw environments variables?

KKimitri is safe expose ids from wrangler binds in an public repository? There's some way...

C

Cyb3r-Jak3•11/16/24, 9:52 AM

Everything in the wrangler file is safe to expose. The only exception is stuff like API keys which you should be using secrets for.

CCyb3r-Jak3 Everything in the wrangler file is safe to expose. The only exception is stuff l...

K

Kimitri•11/16/24, 9:55 AM

Thank you, I had this question because I didn't know if someone can access my Cloudflare resources with bind ids exposed in a wrangle file in a public repository

O

oof2win2•11/17/24, 9:44 PM

is

experimental-json-config

experimental-json-config

safe to use with wrangler? or are there some pitfalls that i should know about if i want to use a json config instead

O

oof2win2•11/17/24, 9:53 PM

that sounds very usable - thank you!

A

Adam•11/18/24, 7:12 PM

is there any way to decide per-binding whether to use local vs remote? I have a problem where I want to develop some changes to a durable object script bound to a worker, but that worker needs to be bound to a remote r2 bucket in order to work. So I want to the locally running worker to the local durable object instance, but keep the remote binding to r2..

K

kaelys.js•11/19/24, 6:20 AM

Is there any way to run analytics engine bindings locally via wrangler or otherwise?

Kkaelys.js Is there any way to run analytics engine bindings locally via wrangler or otherw...

H

Hello, I’m Allie!•11/19/24, 2:51 PM

Not at the moment. I know there was some talk about stubbing them out at some point, but I don’t think that has happened yet

K

Kirk Ouimet•11/19/24, 11:11 PM

Is it possible to run wrangler dev with HTTPS enabled? I have

HTTP Only

HTTP Only

cookies that need to get sent and chrome will not do that unless HTTPS is on

KKirk Ouimet Is it possible to run wrangler dev with HTTPS enabled? I have `HTTP Only` cookie...

C

Cyb3r-Jak3•11/20/24, 1:18 AM

If you use

wrangler dev --local-protocol https

wrangler dev --local-protocol https

. It should work

C

Cyb3r-Jak3•11/20/24, 1:19 AM

It well be a self signed cert. You can pass --https-key-path and --https-cert-path to use your own certificate and key

K

Kirk Ouimet•11/20/24, 1:53 AM

Awesome thank you!

J

James•11/20/24, 4:53 AM

Hey can I change for how long I authorize wrangler to access my account for?

It seems like I used to get a day or so when I authorized wrangler local dev to use tools like Workers AI calls. Now I need to re-auth every few minutes and it's pretty irritating.

JJames Hey can I change for how long I authorize wrangler to access my account for? It...

H

Hello, I’m Allie!•11/20/24, 5:02 AM

IIRC as long as it is used, it should work indefinitely, or at least I’ve never been automatically logged out by it before

out of interest does `--x-dev-env=false` fix it? (it shouldn't but i can't see any other changes tha

Similar Threads

Similar Threads

Similar Threads