Yeah, `queue` handlers don't need to return anything so: `Promise<void>` works well

Yeah,

queue

queue

handlers don't need to return anything so:

Promise<void>

Promise<void>

works well

LordSilver•5/21/24, 6:15 PM

but

satisfies

satisfies

operatore introduced in TypeScript 4.9 shouldn't just check that the function matches expect class?

JJames Yeah, `queue` handlers don't need to return anything so: `Promise<void>` works w...

LordSilver•5/21/24, 6:15 PM

ok but how does it make sure that

batch

batch

is of type

MessageBatch

MessageBatch

LordSilver•5/21/24, 6:16 PM

inside the code i think you would miss some stuff

JamesOP•5/21/24, 6:16 PM

ExportedHandler

ExportedHandler

takes other generic types, included one for

MessageBatch

MessageBatch

JamesOP•5/21/24, 6:16 PM

satisfies

satisfies

covers most of the function. But the return type being explicit creates better errors for DX.

JamesOP•5/21/24, 6:16 PM

That github PR I linked above and discussion that follows is a good reference.

JamesOP•5/21/24, 6:17 PM

As for MessageBatch: https://github.com/Cloudflare-Mining/Cloudflare-Datamining/blob/b7da71b1db954d604955d62c702b955d5e612173/data/workers-types/experimental/index.ts#L409

JamesOP•5/21/24, 6:17 PM

ExportedHandler<Env, MessageBatch>

ExportedHandler<Env, MessageBatch>

for example

LordSilver•5/21/24, 6:17 PM

docs are messy

LordSilver•5/21/24, 6:17 PM

they use half in one way, half in another way, another portion without anything lol

JamesOP•5/21/24, 6:17 PM

File an issue if you find any

Many won't have type arguments though - they're JavaScript (not TypeScript) examples

LordSilver•5/21/24, 6:18 PM

okok so that's the new best way i see

JamesOP•5/21/24, 6:19 PM

Yes, the "best" and recommended way now is

satisfies

satisfies

return type annotation. Like this: https://canary.discord.com/channels/595317990191398933/799437470004412476/1242537864642822245

LordSilver•5/21/24, 6:19 PM

i see many docs also still explicitly put the

Env

Env

in the

index.ts

index.ts

even tho now that's automatically generated in

worker-configuration.d.ts

worker-configuration.d.ts

LordSilver•5/21/24, 6:19 PM

i guess that was also recent addition

JamesOP•5/21/24, 6:20 PM

Yeah that's super new, and not something I'm personally a fan of, but hey

JamesOP•5/21/24, 6:20 PM

It allows for good types generation via

wrangler types

wrangler types

tho

LordSilver•5/21/24, 6:22 PM

is there a way to further improve this too?

JamesOP•5/21/24, 6:23 PM

I'd add an explicit return type annotation on

fetch

fetch

: Promise<Response>

: Promise<Response>

so ts will catch if you ever accidentally return something else

JamesOP•5/21/24, 6:23 PM

otherwise seems good

LordSilver•5/21/24, 6:24 PM

JJames I'd add an explicit return type annotation on `fetch` as `: Promise<Response>` s...

DaniFoldi•5/22/24, 8:31 AM

fun fact

Response | Promise<Response>

Response | Promise<Response>

is implied from

implements DurableObject

implements DurableObject

Varna•5/22/24, 10:50 AM

Is it possible to mimic worker routes in localhost with wrangler?

# wrangler.toml
# ...

routes = [
  { pattern = "example.test/api*", zone_name = "example.test" },
  { pattern = "localhost:4321/api*", zone_name = "localhost" },
]

# wrangler.toml
# ...

routes = [
  { pattern = "example.test/api*", zone_name = "example.test" },
  { pattern = "localhost:4321/api*", zone_name = "localhost" },
]

VVarna Is it possible to mimic worker routes in localhost with wrangler? ```toml # wran...

Hello, I’m Allie!•5/22/24, 10:54 AM

Afaik no

tstststs•5/22/24, 2:54 PM

Hello.
I'm developing a worker that uploads files to R2. For local dev, is there a way to emulate S3 compatible endpoint that would serve/upload the files stored in the --persist-to dir that my worker is using?

Ttstststs Hello. I'm developing a worker that uploads files to R2. For local dev, is there...

Hello, I’m Allie!•5/22/24, 3:08 PM

Not at the moment, no

tstststs•5/22/24, 3:08 PM

thanks

kingmesal•5/22/24, 11:10 PM

I ran into a really ODD problem that I don't think should happen. with the following wrangler toml

d1_databases = [
  { binding = "DB", database_name = "mydb", database_id = "id1", preview_database_id = "id2" },
]

d1_databases = [
  { binding = "DB", database_name = "mydb", database_id = "id1", preview_database_id = "id2" },
]

When running

wrangler dev --remote

wrangler dev --remote

the preview_database_id is used. Perfect! However, when running

wrangler dev

wrangler dev

the preview_database_id is used.

If I change to:

d1_databases = [
  { binding = "DB", database_name = "mydb", database_id = "id1" },
]

d1_databases = [
  { binding = "DB", database_name = "mydb", database_id = "id1" },
]

When running

wrangler dev

wrangler dev

the database_id is used.

I thought the whole point of preview_database_id was for the remote use. Is this officially a bug? This seems very illogical.

kian•5/22/24, 11:20 PM

preview is just for development in general, not specifically remote

Kkian preview is just for development in general, not specifically remote

kingmesal•5/23/24, 3:27 PM

this is kind of terrible for DEV mode though ... i have two workers, one I run --remote and the other not, but if I use the same database spec, they will not use the same local D1 when i run them both remote

richtera•5/23/24, 4:43 PM

Asking about roles again. I am really struggling with integrating wrangler stuff with our infrastructure using git or cloudflare builds, because I cannot give access to a developer on a pages or wrangler project level. I cannot give them access to logs on cloudflare builds and I cannot lock down which project they deploy on using git ops builds. Will this be fixed soon?

Mitya•5/24/24, 2:57 PM

Getting Wrangler errors on some CI deployments via GH action. Normally they go through fine, but sometimes they fail with Error: The process '/usr/local/bin/npx' failed with exit code 1Error: The process '/usr/local/bin/npx' failed with exit code 1. Despite that, on the CF side, it seems to show that the deployments were successful - it shows that the active deployment was made "a few seconds ago". Any thoughts?

Mitya•5/24/24, 3:47 PM

Anyone from CF around? ^^

MMitya Getting Wrangler errors on some CI deployments via GH action. Normally they go t...

Ian•5/27/24, 1:27 AM

What is the actual error? npx is the caller but it's at the top of the chain so saying it failed isn't very helpful.

renox•6/1/24, 3:41 AM

How can i do wrangler login without the browser? i want to create r2 buckets from the cli but i need the login process automated without a browser

Rrenox How can i do wrangler login without the browser? i want to create r2 buckets fro...

Erisa•6/1/24, 11:42 AM

Create an API token and set CLOUDFLARE_API_TOKENCLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_IDCLOUDFLARE_ACCOUNT_ID environment variables

Erisa•6/1/24, 11:42 AM

https://developers.cloudflare.com/workers/wrangler/migration/v1-to-v2/wrangler-legacy/authentication/#using-environment-variables

Cloudflare Docs

Authentication · Cloudflare Workers docs

This page is for Wrangler v1, which has now been deprecated. Access documentation for the current version of Wrangler by visiting the Wrangler …

gekkepop.•6/2/24, 10:17 AM

Hi, I get this error:

wrangler 3.58.0
-------------------

X [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. wrangler deploy path/to/scriptwrangler deploy path/to/script) or the
main
main
config field.

Problem is, I do have the field:
main = "src/index.js"

But even manually saying:

wrangler deploy "src/index.js"

doesn't work, keeps saying I am missing my entry-point.

Any idea what I am doing wrong?

Ggekkepop.Hi, I get this error: > wrangler 3.58.0 > ------------------- > > X [ERROR] Mi...

Hello, I’m Allie!•6/2/24, 10:18 AM

Can you paste your entire

wrangler.toml

wrangler.toml

HHello, I’m Allie!Can you paste your entire `wrangler.toml`?

gekkepop.•6/2/24, 10:20 AM

#:schema node_modules/wrangler/config-schema.json
name = "secretname"
main = "src/index.js"
compatibility_date = "2024-05-29"

[[durable_objects.bindings]]
name = "roomObject"
class_name = "RoomObject"

#[[migrations]]
#tag = "v2"
#renamed_classes = [{from = "MyDurableObject", to = "RoomObject" }] # Array of rename directives
#deleted_classes = ["MyDurableObject"] # Array of deleted class names

[[kv_namespaces]]
binding = "name"
id = "12345"

gekkepop.•6/2/24, 10:20 AM

Only thing new is my new kv_namespaces, nothing else changed really

gekkepop.•6/2/24, 10:29 AM

BTW, the logs I get in the error aren't helpful either, it literally only says: Writing logs to "location"

gekkepop.•6/2/24, 10:31 AM

If I do:

wrangler deploy "src/index.js"

I get:

The entry-point file at "src\index.js" was not found.

So it seems like it somehow can't see my files? Even though my project structure hasn't changed

gekkepop.•6/2/24, 10:56 AM

Lol, I can't even do this (from project folder):

cd src

Gives:

Set-Location: Cannot find path 'C:\Data\WranglerProjects\workerProject\src' because it does not exist.

gekkepop.•6/2/24, 10:56 AM

I can open it using file explorer though, what is going on?!

gekkepop.•6/2/24, 10:59 AM

I got it! My entire folder structure got screwed over, so stuff was nested with the same name

gekkepop.•6/2/24, 11:00 AM

So it was looking into a nested folder with exactly the same name, but it was the wrong folder

IIan What is the actual error? npx is the caller but it's at the top of the chain so ...

Mitya•6/4/24, 9:58 AM

I just reported what the error said - I wasn't to know that that is apparently "unhelpful". Here's the screenshot of what I see: https://discord.com/channels/595317990191398933/1243576135464390726/1243577874326224946

Tempo•6/4/24, 6:40 PM

Hi, is it possible to use wrangler to dev localy but with a remote r2 ?

Yeah, `queue` handlers don't need to return anything so: `Promise<void>` works well

Similar Threads