I used to use ```npx wrangler deploy --dry-run --outdir=dist``` in my project, but since today (

Mmackenzie I used to use ```npx wrangler deploy --dry-run --outdir=dist``` in my projec...

K

kian•5/21/24, 8:17 AM

They haven't been removed, they're still there.

M

mackenzieOP•5/21/24, 8:38 AM

hmmmm, not sure what causes that error message "✘ [ERROR] Unknown arguments: dry-run, dryRun, outdir, deploy" .... repeating I get:

npx wrangler deploy --dry-run --outdir=dist
 ⛅️ wrangler 3.57.0
-------------------

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

npx wrangler deploy --dry-run --outdir=dist
 ⛅️ wrangler 3.57.0
-------------------

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

npx wrangler deploy --dry-run --outdir=dist
 ⛅️ wrangler 3.57.0
-------------------

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

npx wrangler deploy --dry-run --outdir=dist
 ⛅️ wrangler 3.57.0
-------------------

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

not sure how "main" should be used, or is a script reference missing?

K

kian•5/21/24, 8:40 AM

Means it can't find a Wrangler.toml in that folder, usually

M

mackenzieOP•5/21/24, 8:40 AM

wrangler

Commands:
  wrangler docs [command..]            📚 Open wrangler's docs in your browser
  wrangler init [name]                 📥 Initialize a basic Worker project, including a wrangler.toml file
  wrangler generate [name] [template]  ✨ Generate a new Worker project from an existing Worker template. See https://github.com/cloudflare/templates
  wrangler dev [script]                👂 Start a local server for developing your worker
  wrangler publish [script]            🆙 Publish your Worker to Cloudflare.
  wrangler delete [script]             🗑  Delete your Worker from Cloudflare.
  wrangler tail [worker]               🦚 Starts a log tailing session for a published Worker.
...elided...
  wrangler login                       🔓 Login to Cloudflare
  wrangler logout                      🚪 Logout from Cloudflare
  wrangler whoami                      🕵️  Retrieve your user info and test your auth config
  wrangler types                       📝 Generate types from bindings & module rules in config
  wrangler deployments                 🚢 List and view details for deployments
  wrangler rollback [deployment-id]    🔙 Rollback a deployment
...

wrangler

Commands:
  wrangler docs [command..]            📚 Open wrangler's docs in your browser
  wrangler init [name]                 📥 Initialize a basic Worker project, including a wrangler.toml file
  wrangler generate [name] [template]  ✨ Generate a new Worker project from an existing Worker template. See https://github.com/cloudflare/templates
  wrangler dev [script]                👂 Start a local server for developing your worker
  wrangler publish [script]            🆙 Publish your Worker to Cloudflare.
  wrangler delete [script]             🗑  Delete your Worker from Cloudflare.
  wrangler tail [worker]               🦚 Starts a log tailing session for a published Worker.
...elided...
  wrangler login                       🔓 Login to Cloudflare
  wrangler logout                      🚪 Logout from Cloudflare
  wrangler whoami                      🕵️  Retrieve your user info and test your auth config
  wrangler types                       📝 Generate types from bindings & module rules in config
  wrangler deployments                 🚢 List and view details for deployments
  wrangler rollback [deployment-id]    🔙 Rollback a deployment
...

wrangler

Commands:
  wrangler docs [command..]            📚 Open wrangler's docs in your browser
  wrangler init [name]                 📥 Initialize a basic Worker project, including a wrangler.toml file
  wrangler generate [name] [template]  ✨ Generate a new Worker project from an existing Worker template. See https://github.com/cloudflare/templates
  wrangler dev [script]                👂 Start a local server for developing your worker
  wrangler publish [script]            🆙 Publish your Worker to Cloudflare.
  wrangler delete [script]             🗑  Delete your Worker from Cloudflare.
  wrangler tail [worker]               🦚 Starts a log tailing session for a published Worker.
...elided...
  wrangler login                       🔓 Login to Cloudflare
  wrangler logout                      🚪 Logout from Cloudflare
  wrangler whoami                      🕵️  Retrieve your user info and test your auth config
  wrangler types                       📝 Generate types from bindings & module rules in config
  wrangler deployments                 🚢 List and view details for deployments
  wrangler rollback [deployment-id]    🔙 Rollback a deployment
...

wrangler

Commands:
  wrangler docs [command..]            📚 Open wrangler's docs in your browser
  wrangler init [name]                 📥 Initialize a basic Worker project, including a wrangler.toml file
  wrangler generate [name] [template]  ✨ Generate a new Worker project from an existing Worker template. See https://github.com/cloudflare/templates
  wrangler dev [script]                👂 Start a local server for developing your worker
  wrangler publish [script]            🆙 Publish your Worker to Cloudflare.
  wrangler delete [script]             🗑  Delete your Worker from Cloudflare.
  wrangler tail [worker]               🦚 Starts a log tailing session for a published Worker.
...elided...
  wrangler login                       🔓 Login to Cloudflare
  wrangler logout                      🚪 Logout from Cloudflare
  wrangler whoami                      🕵️  Retrieve your user info and test your auth config
  wrangler types                       📝 Generate types from bindings & module rules in config
  wrangler deployments                 🚢 List and view details for deployments
  wrangler rollback [deployment-id]    🔙 Rollback a deployment
...

I don't see deploy in that list...., but it still works I guess....

M

mackenzieOP•5/21/24, 8:43 AM

there's a wrangler.toml (lowercase 'W')

M

mackenzieOP•5/21/24, 8:44 AM

I'm confused:

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

M

mackenzieOP•5/21/24, 8:46 AM

woa...

npx wrangler --version
 ⛅️ wrangler 2.21.1 (update available 3.57.0)
-------------------------------------------------------
andrew@amackenz-mac collectr % wrangler --version 
 ⛅️ wrangler 3.57.0
-------------------

npx wrangler --version
 ⛅️ wrangler 2.21.1 (update available 3.57.0)
-------------------------------------------------------
andrew@amackenz-mac collectr % wrangler --version 
 ⛅️ wrangler 3.57.0
-------------------

npx wrangler --version
 ⛅️ wrangler 2.21.1 (update available 3.57.0)
-------------------------------------------------------
andrew@amackenz-mac collectr % wrangler --version 
 ⛅️ wrangler 3.57.0
-------------------

npx wrangler --version
 ⛅️ wrangler 2.21.1 (update available 3.57.0)
-------------------------------------------------------
andrew@amackenz-mac collectr % wrangler --version 
 ⛅️ wrangler 3.57.0
-------------------

Mmackenzie woa... ``` npx wrangler --version ⛅️ wrangler 2.21.1 (update available 3.57.0)...

H

Hello, I’m Allie!•5/21/24, 8:47 AM

That's a tricky bugger right there. We recommend installing

wrangler

wrangler

wrangler

wrangler within a project, then calling it from there, so that you consitently use the same version

M

mackenzieOP•5/21/24, 8:47 AM

is it recommended calling directly, or via npx?
(I know virtually zero about npm and npx)

M

mackenzieOP•5/21/24, 8:48 AM

scripts in jsons seem to use npx

M

mackenzieOP•5/21/24, 8:48 AM

in .ts sorry

Mmackenzie is it recommended calling directly, or via npx? (I know virtually zero about npm...

H

Hello, I’m Allie!•5/21/24, 8:48 AM

Calling directly is what I do, though afaik

npm

npm

doesn't actually support that for arbitrary commands, so

npx

npx

would probably be the next best thing.

H

Hello, I’m Allie!•5/21/24, 8:49 AM

I use

pnpm

pnpm

pnpm

pnpm for arbitrary command execution using the locally installed package:

pnpm wrangler deploy [whatever]

pnpm wrangler deploy [whatever]

pnpm wrangler deploy [whatever]

pnpm wrangler deploy [whatever]

M

mackenzieOP•5/21/24, 8:51 AM

I have multiple folders (a worker, a pages app, functions) - so maybe I need to upgrade wrangler in all of them when updating?

M

mackenzieOP•5/21/24, 8:55 AM

OK, for now I'm calling wrangler directly and it's solved that....now to fix broken Leptos app that won't deploy

E

Eai•5/21/24, 1:06 PM

Hello, I'm thinking of using an API token because wrangler's oauth doesn't support multiple accounts.
How can I create an API token with privileges equivalent to wrangler login?
That is, an API token that has these permissions:
account:read
user:read
zone:read
workers:write
workers_kv:write
workers_routes:write
workers_scripts:write
workers_tail:read
d1:write
pages:write
ssl_certs:write
constellation:write
ai:write
queues:write
offline_access

L

LordSilver•5/21/24, 4:01 PM

do you guys use the

satisfies

satisfies

satisfies

satisfies in your workers?

L

LordSilver•5/21/24, 4:01 PM

i see it's present in some parts of the docs and not present in others

L

LordSilver•5/21/24, 4:01 PM

in other parts they use the types on the parameters instead

LLordSilver do you guys use the `satisfies` in your workers?

J

James•5/21/24, 6:01 PM

short answer: a combo of both provides the best DX.

export default {
    async fetch(request, env, ctx): Promise<Response> {
        // do things
    },
} satisfies ExportedHandler<Env>;

export default {
    async fetch(request, env, ctx): Promise<Response> {
        // do things
    },
} satisfies ExportedHandler<Env>;

export default {
    async fetch(request, env, ctx): Promise<Response> {
        // do things
    },
} satisfies ExportedHandler<Env>;

export default {
    async fetch(request, env, ctx): Promise<Response> {
        // do things
    },
} satisfies ExportedHandler<Env>;

long answer: https://github.com/cloudflare/cloudflare-docs/pull/14007

JJames short answer: a combo of both provides the best DX. ```ts export default { ...

L

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

the one you are using misses stuff

L

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

You could use

request: Request

request: Request

request: Request

request: Request,

env: Env

env: Env

env: Env

env: Env

J

James•5/21/24, 6:12 PM

You don't need those with

satisfies ExportedHandler<Env>

satisfies ExportedHandler<Env>

satisfies ExportedHandler<Env>

satisfies ExportedHandler<Env>

the arguments are already typed

L

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

in some cases you also have extra stuff like here message batch

L

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

also this is not needed?

J

James•5/21/24, 6:13 PM

That could be refactored to use

ExportedHandler

ExportedHandler

ExportedHandler

ExportedHandler

return type annotation too, yes

L

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

return type annotation?

L

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

promise void u mean?

J

James•5/21/24, 6:13 PM

All you need is the return type like

: Promise<Response>

: Promise<Response>

: Promise<Response>

: Promise<Response> for better DX, and then

satisfies ExportedHandler<Env>;

satisfies ExportedHandler<Env>;

satisfies ExportedHandler<Env>;

satisfies ExportedHandler<Env>;

J

James•5/21/24, 6:14 PM

Yeah,

queue

queue

queue

queue handlers don't need to return anything so:

Promise<void>

Promise<void>

Promise<void>

Promise<void> works well

L

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

but

satisfies

satisfies

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...

L

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

ok but how does it make sure that

batch

batch

batch

batch is of type

MessageBatch

MessageBatch

MessageBatch

MessageBatch?

L

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

inside the code i think you would miss some stuff

J

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

ExportedHandler

ExportedHandler

ExportedHandler

ExportedHandler takes other generic types, included one for

MessageBatch

MessageBatch

MessageBatch

MessageBatch

J

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

satisfies

satisfies

satisfies

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

J

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

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

J

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

J

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

ExportedHandler<Env, MessageBatch>

ExportedHandler<Env, MessageBatch>

ExportedHandler<Env, MessageBatch>

ExportedHandler<Env, MessageBatch> for example

L

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

docs are messy

L

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

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

J

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

L

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

okok so that's the new best way i see

J

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

Yes, the "best" and recommended way now is

satisfies

satisfies

satisfies

satisfies

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

L

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

i see many docs also still explicitly put the

Env

Env

Env

Env in the

index.ts

index.ts

even tho now that's automatically generated in

worker-configuration.d.ts

worker-configuration.d.ts

worker-configuration.d.ts

worker-configuration.d.ts

L

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

i guess that was also recent addition

J

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

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

J

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

It allows for good types generation via

wrangler types

wrangler types

tho

L

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

is there a way to further improve this too?

J

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

I'd add an explicit return type annotation on

fetch

fetch

as

: Promise<Response>

: Promise<Response>

: Promise<Response>

: Promise<Response> so ts will catch if you ever accidentally return something else

J

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

otherwise seems good

I used to use ```npx wrangler deploy --dry-run --outdir=dist``` in my project, but since today (

Similar Threads

Similar Threads

Similar Threads