Skip to content

Commit 66508f7

Browse files
committed
adds bindings_per_env.mdx under src/content/partials/workers
1 parent 22dd07e commit 66508f7

File tree

2 files changed

+33
-28
lines changed

2 files changed

+33
-28
lines changed

src/content/docs/workers/local-development/wrangler.mdx

Lines changed: 2 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ head: []
77
description: Locally develop and test changes with `wrangler dev`
88
---
99

10-
import { PackageManagers } from "~/components";
10+
import { Render, PackageManagers } from "~/components";
1111

1212
## Start a local development server
1313

@@ -25,33 +25,7 @@ Wrangler provides a [`dev`](/workers/wrangler/commands/#dev) command that starts
2525

2626
`wrangler dev` will run the Worker directly on your local machine. `wrangler dev` uses a combination of `workerd` and [Miniflare](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare), a simulator that allows you to test your Worker against additional resources like KV, Durable Objects, WebSockets, and more.
2727

28-
### Supported resource bindings in different environments
29-
30-
| Product | Local Dev Supported | Remote Dev Supported |
31-
| ----------------------------------- | ------------------- | -------------------- |
32-
| AI |[^1] ||
33-
| Assets |||
34-
| Analytics Engine |||
35-
| Browser Rendering |||
36-
| D1 |||
37-
| Durable Objects |||
38-
| Email Bindings |||
39-
| Hyperdrive |||
40-
| Images |||
41-
| KV |||
42-
| mTLS |||
43-
| Queues |||
44-
| R2 |||
45-
| Rate Limiting |||
46-
| Service Bindings (multiple Workers) |||
47-
| Vectorize |[^2] ||
48-
| Workflows |||
49-
50-
With any bindings that are not supported locally, you will need to use the [`--remote` command](#develop-using-remote-resources-and-bindings) in wrangler, such as `wrangler dev --remote`.
51-
52-
[^1]: Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
53-
54-
[^2]: Using Vectorize always accesses your Cloudflare account to run queries, and will incur usage charges even in local development.
28+
<Render file="bindings_per_env" />
5529

5630
## Work with local data
5731

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
{}
3+
---
4+
5+
### Supported resource bindings in different environments
6+
7+
| Product | Local Dev Supported | Remote Dev Supported |
8+
| ----------------------------------- | ------------------- | -------------------- |
9+
| AI |[^1] ||
10+
| Assets |||
11+
| Analytics Engine |||
12+
| Browser Rendering |||
13+
| D1 |||
14+
| Durable Objects |||
15+
| Email Bindings |||
16+
| Hyperdrive |||
17+
| Images |||
18+
| KV |||
19+
| mTLS |||
20+
| Queues |||
21+
| R2 |||
22+
| Rate Limiting |||
23+
| Service Bindings (multiple Workers) |||
24+
| Vectorize |[^2] ||
25+
| Workflows |||
26+
27+
With any bindings that are not supported locally, you will need to use the [`--remote` command](#develop-using-remote-resources-and-bindings) in wrangler, such as `wrangler dev --remote`.
28+
29+
[^1]: Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
30+
31+
[^2]: Using Vectorize always accesses your Cloudflare account to run queries, and will incur usage charges even in local development.

0 commit comments

Comments
 (0)