I’m trying to understand the relationship between all the cloudflare sdk tools. Could you correct m

I

IEatBeansOP•5/14/24, 4:55 PM

Or do I still need wrangler

IIEatBeans I’m trying to understand the relationship between all the cloudflare sdk tools. ...

R

robmarscher•5/15/24, 2:15 PM

I used to create a miniflare server directly for testing. You should be able to start it from a node script without wrangler. https://www.npmjs.com/package/miniflare

Z

zwily•5/16/24, 7:35 PM

Is there a way to bind the same local KV store to 2 different apps when developing locally?

Zzwily Is there a way to bind the same *local* KV store to 2 different apps when develo...

H

Hello, I’m Allie!•5/16/24, 7:36 PM

Use

--persist-to

--persist-to

to point them both to the same directory. As long as they have the same ID, they should pull from the same place

HHello, I’m Allie!Use `--persist-to` to point them both to the same directory. As long as they hav...

Z

zwily•5/16/24, 7:36 PM

Awesome thanks.

J

Jacob Marshall•5/16/24, 7:44 PM

Has anybody run into issues (or is it a common issue) with R2 bindings running locally via wrangler, where binary data (eg. a png) is corrupted when downloaded (

env.R2.get(...)

env.R2.get(...)

). And appears the encoding is borked somewhere along the way. I can see that the file is not corrupted on the disk (within the

.wrangler

.wrangler

folder) but when I download the file, via the worker, it "corrupts". I the screenshot attached, the left is the original file, and the right is after downloading from R2. It's worth mentioning that if I upload a text file (eg. xml) - it works fine.

J

Jacob Marshall•5/16/24, 7:45 PM

Running the same code on an actual Cloudflare Worker works fine.

B

Billy•5/17/24, 8:14 PM

I started seeing authz errors today when trying to import data to a newly created db.

wrangler d1 execute <DBNAME> --remote --file=./creation_insertion_stmts.sql

wrangler d1 execute <DBNAME> --remote --file=./creation_insertion_stmts.sql

is now giving me this:

 ⛅️ wrangler 3.57.0
-------------------
✔ ⚠️ This process may take some time, during which your D1 database will be unavailable to serve queries.
  Ok to proceed? … yes
🌀 Executing on remote database <DBNAME> (***):
🌀 To execute on your local development database, remove the --remote flag from your wrangler command.
Note: if the execution fails to complete, your DB will return to its original state and you can safely retry.
🌀 File already uploaded. Processing.
🌀 Starting import...
🌀 not authorized

✘ [ERROR]

  Starting import...
  not authorized

 ⛅️ wrangler 3.57.0
-------------------
✔ ⚠️ This process may take some time, during which your D1 database will be unavailable to serve queries.
  Ok to proceed? … yes
🌀 Executing on remote database <DBNAME> (***):
🌀 To execute on your local development database, remove the --remote flag from your wrangler command.
Note: if the execution fails to complete, your DB will return to its original state and you can safely retry.
🌀 File already uploaded. Processing.
🌀 Starting import...
🌀 not authorized

✘ [ERROR]

  Starting import...
  not authorized

 ⛅️ wrangler 3.57.0
-------------------
✔ ⚠️ This process may take some time, during which your D1 database will be unavailable to serve queries.
  Ok to proceed? … yes
🌀 Executing on remote database <DBNAME> (***):
🌀 To execute on your local development database, remove the --remote flag from your wrangler command.
Note: if the execution fails to complete, your DB will return to its original state and you can safely retry.
🌀 File already uploaded. Processing.
🌀 Starting import...
🌀 not authorized

✘ [ERROR]

  Starting import...
  not authorized

 ⛅️ wrangler 3.57.0
-------------------
✔ ⚠️ This process may take some time, during which your D1 database will be unavailable to serve queries.
  Ok to proceed? … yes
🌀 Executing on remote database <DBNAME> (***):
🌀 To execute on your local development database, remove the --remote flag from your wrangler command.
Note: if the execution fails to complete, your DB will return to its original state and you can safely retry.
🌀 File already uploaded. Processing.
🌀 Starting import...
🌀 not authorized

✘ [ERROR]

  Starting import...
  not authorized

I just updated wrangler to 3.57.0. I'll report if someone thinks it might be a bug. Thanks

K

kian•5/17/24, 8:20 PM

not authorized means you tried using a pragma/function that isn't allowlisted

Kkian not authorized means you tried using a pragma/function that isn't allowlisted

B

Billy•5/17/24, 8:21 PM

Thank you, I do have that

PRAGMA foreign_keys=OFF;

PRAGMA foreign_keys=OFF;

K

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

D1’s foreign key enforcement is equivalent to SQLite’s PRAGMA foreign_keys = on directive. Because D1 runs every query inside an implicit transaction, user queries cannot change this during a query or migration.

K

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

https://developers.cloudflare.com/d1/build-with-d1/foreign-keys/

K

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

You can use

defer_foreign_keys

defer_foreign_keys

though

Kkian > D1’s foreign key enforcement is equivalent to SQLite’s PRAGMA foreign_keys = o...

B

Billy•5/17/24, 8:26 PM

thank you, looks like I need to start leaving off the

BEGIN TRANSACTION;

BEGIN TRANSACTION;

and

COMMIT;

COMMIT;

as well. I'll review that allowlist. Thanks again, I've been able to import everything remotely now.

https://developers.cloudflare.com/d1/build-with-d1/import-data/#convert-sqlite-database-files

I missed the change.

Cloudflare Docs

Import data · Cloudflare D1 docs

D1 allows you to import existing SQLite tables and their data directly, enabling you to migrate existing data into D1 quickly and easily. This can be …

M

mackenzie•5/21/24, 8:15 AM

I used to use

npx wrangler deploy --dry-run --outdir=dist

npx wrangler deploy --dry-run --outdir=dist

in my project, but since today (it's been a few days since I haven't toucher it though) I get an error for that:

✘ [ERROR] Unknown arguments: dry-run, dryRun, outdir, deploy

✘ [ERROR] Unknown arguments: dry-run, dryRun, outdir, deploy

and I can't see the arguments that replace that feature.

wrangler --version
 ⛅️ wrangler 3.57.0

wrangler --version
 ⛅️ wrangler 3.57.0

what should I use now to replace that?

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

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

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

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

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

M

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

I'm confused:

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

npx wrangler deploy

✘ [ERROR] Unknown argument: deploy

M

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

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

M

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

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

M

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

scripts in jsons seem to use npx

M

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

for arbitrary command execution using the locally installed package:

pnpm wrangler deploy [whatever]

pnpm wrangler deploy [whatever]

M

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

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

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

,

env: Env

env: Env

J

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

You don't need those with

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

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?

I’m trying to understand the relationship between all the cloudflare sdk tools. Could you correct m

Similar Threads