Cloudflare

because now I want to get better at wranglers.

`routes = [

    { pattern = "https://domain.com/*", zone_id = "<zone_id>" }
]

workers_dev = false`

Are you sure the domain and zone ID are correct? Did you re-upload the worker? Did you get any errors/warnings in the output of wrangler when you did that?

no. i edited this code and added it to the bottom line of the `toml file` and 
I ran the `wrangler deploy` code

Did you get any errors/warnings in the output of wrangler when you did that?


https://cdn.discordapp.com/attachments/799437470004412476/1112331341653094550/Screenshot_10.png

If you look on the dashboard now, do you see the route you configured there?

Can you DM me your entire wrangler.toml file?

Thanks for the help <@269867330526248960> 
Problem solved

<@1095376375302590547> you'll want to keep that file in case you ever need to recreate the database or anything like that

I got it. so how can I apply the database I created with schema.sql to my worker

ie: when I run the wrangler deploy code, the information in the schema.sql code is not applied to my worker

Not automatically, no. You need to run a seperate command to do that

`wrangler d1 execute <DATABASE_NAME> --file=./schema.sql`

hi, i have a (dumb) question: i'm not sure what exactly is the correct approach for the d1 configuration in the wrangler.toml and more precisely should the db name and id be clear text or should they be secrets?

It is fine to have in plain text. They are not sensitive just uuid4s

Ctrl-C or `x` does not change anything it stays on:
```.../node_modules/.pnpm/@cloudflare+workerd-darwin-arm64@1.20231030.0/node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd serve --binary --experimental --socket-addr=entry=localhost:4242 --external-addr=loopback=localhost:57867 --control-fd=3 -```

It looks like this is a bug with a recent version of wrangler/workerd: https://github.com/cloudflare/workers-sdk/issues/4612

We are working to resolve it.

<@1040133239135817809> if you have time to have a look in <#1052656806058528849> I have a quick question about dns resolution inside a worker. Which seems to behave differently when reach on a custom domain versus worker.dev

https://discord.com/channels/595317990191398933/1186554218224554014

hello, kind of new in the game but it

That is a great suggestion. We "rebuilt" the esbuild options with plugins etc internally to get a similar enough file that we can use to analyze the bundle.

esbuild

I'd recommend making an issue for the feature request on <https://github.com/cloudflare/workers-sdk/issues> - it's unlikely to be seen by the team here.

Of course: https://github.com/cloudflare/workers-sdk/issues/4633

<@955408965968228372> btw an alternative way to do this is you can just edit the code path to write the json in wrangler, and use something like a pnpm patch

That would have been a pretty smart idea honestly, vs. my rebuilding the whole `esbuild` config until I had a similar enough result 😄

Could a `metafile` option be added to

In case I use `--no-bundle` it works under `wrangler pages dev`!