[All] Cleaning up references to wrangler.toml. (#19403)

* Cleaning up references to wrangler.toml.

* Removing erroneous import line.

* Making sure all imports are at the top of the page.

* Catching more instances of wrangler.toml.

* Fixing typo

* Update src/content/docs/workers/platform/pricing.mdx

Co-authored-by: marciocloudflare <[email protected]>

* Update src/content/docs/workers/languages/python/index.mdx

Co-authored-by: marciocloudflare <[email protected]>

* Syntax formatting and edit for accuracy.

* Updating language to `wrangler.toml / wrangler.json`

---------

Co-authored-by: marciocloudflare <[email protected]>

Author: 2 people

src/content/changelogs/queues.yaml

@@ -64,7 +64,7 @@ entries:
     description: |-
       Queue consumers will soon automatically scale up concurrently as a queues' backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.
 
-      **To opt-out, or to configure a fixed maximum concurrency**, set `max_concurrency = 1` in your `wrangler.toml` file or via [the queues dashboard](https://dash.cloudflare.com/?to=/:account/queues).
+      **To opt-out, or to configure a fixed maximum concurrency**, set `max_concurrency = 1` in your `wrangler.toml / wrangler.json` file or via [the queues dashboard](https://dash.cloudflare.com/?to=/:account/queues).
 
       **To opt-in, you do not need to take any action**: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the [consumer concurrency](/queues/configuration/consumer-concurrency/) documentation.
   - publish_date: "2023-03-02"

src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx

@@ -4,7 +4,7 @@ pcx_content_type: tutorial
 updated: 2024-10-17
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 This guide will walk you through setting up and deploying a Workers AI project. You will use [Workers](/workers/), an AI Gateway binding, and a large language model (LLM), to deploy your first AI-powered application on the Cloudflare global network.
 
@@ -35,7 +35,7 @@ Running `npm create cloudflare@latest` will prompt you to install the create-clo
 This will create a new `hello-ai` directory. Your new `hello-ai` directory will include:
 
 - A "Hello World" Worker at `src/index.ts`.
-- A `wrangler.toml` configuration file.
+- A `wrangler.json` configuration file.
 
 Go to your application directory:
 
@@ -47,9 +47,7 @@ cd hello-ai
 
 You must create an AI binding for your Worker to connect to Workers AI. Bindings allow your Workers to interact with resources, like Workers AI, on the Cloudflare Developer Platform.
 
-To bind Workers AI to your Worker, add the following to the end of your `wrangler.toml` file:
-
-import { WranglerConfig } from "~/components";
+To bind Workers AI to your Worker, add the following to the end of your `wrangler.json` file:
 
 <WranglerConfig>
 
@@ -72,7 +70,7 @@ Update the `index.ts` file in your `hello-ai` application directory with the fol
 
 ```typescript title="src/index.ts" {78-81}
 export interface Env {
-	// If you set another name in wrangler.toml as the value for 'binding',
+	// If you set another name in the `wrangler.toml / wrangler.json` file as the value for 'binding',
 	// replace "AI" with the variable name you defined.
 	AI: Ai;
 }

src/content/docs/analytics/analytics-engine/get-started.mdx

@@ -9,13 +9,11 @@ head:
 
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, WranglerConfig } from "~/components"
 
 ## 1. Name your dataset and add it to your Worker
 
-Add the following to your `wrangler.toml` file to create a [binding](/workers/runtime-apis/bindings/) to a Workers Analytics Engine dataset. A dataset is like a table in SQL: the rows and columns should have consistent meaning.
-
-import { WranglerConfig } from "~/components";
+Add the following to your `wrangler.toml / wrangler.json` file to create a [binding](/workers/runtime-apis/bindings/) to a Workers Analytics Engine dataset. A dataset is like a table in SQL: the rows and columns should have consistent meaning.
 
 <WranglerConfig>
 

src/content/docs/analytics/analytics-engine/worker-querying.mdx

@@ -8,6 +8,9 @@ head:
     content: Querying Workers Analytics Engine from a Worker
 ---
 
+
+import { WranglerConfig } from "~/components";
+
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
 
 ## Authentication
@@ -46,9 +49,7 @@ The following is a sample Worker which executes a query against a dataset of wea
 
 First the environment variables are set up with the account ID and API token.
 
-The account ID is set in `wrangler.toml`:
-
-import { WranglerConfig } from "~/components";
+The account ID is set in the `wrangler.toml / wrangler.json` file:
 
 <WranglerConfig>
 

src/content/docs/browser-rendering/get-started/browser-rendering-with-DO.mdx

@@ -14,7 +14,7 @@ sidebar:
   order: 2
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 By following this guide, you will create a Worker that uses the Browser Rendering API along with [Durable Objects](/durable-objects/) to take screenshots from web pages and store them in [R2](/r2/).
 
@@ -69,13 +69,11 @@ wrangler r2 bucket list
 
 After running the `list` command, you will see all bucket names, including the ones you have just created.
 
-## 5. Configure `wrangler.toml`
+## 5. Configure your Wrangler configuration file
 
-Configure your `browser-worker` project's [`wrangler.toml`](/workers/wrangler/configuration/) file by adding a browser [binding](/workers/runtime-apis/bindings/) and a [Node.js compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag). Browser bindings allow for communication between a Worker and a headless browser which allows you to do actions such as taking a screenshot, generating a PDF and more.
+Configure your `browser-worker` project's [`wrangler.toml / wrangler.json` file](/workers/wrangler/configuration/) by adding a browser [binding](/workers/runtime-apis/bindings/) and a [Node.js compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag). Browser bindings allow for communication between a Worker and a headless browser which allows you to do actions such as taking a screenshot, generating a PDF and more.
 
-Update your `wrangler.toml` configuration file with the Browser Rendering API binding, the R2 bucket you created and a Durable Object:
-
-import { WranglerConfig } from "~/components";
+Update your `wrangler.toml / wrangler.json` file with the Browser Rendering API binding, the R2 bucket you created and a Durable Object:
 
 <WranglerConfig>
 

src/content/docs/browser-rendering/get-started/reuse-sessions.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 The best way to improve the performance of your browser rendering worker is to reuse sessions. One way to do that is via [Durable Objects](/browser-rendering/get-started/browser-rendering-with-do/), which allows you to keep a long running connection from a worker to a browser. Another way is to keep the browser open after you've finished with it, and connect to that session each time you have a new request.
 
@@ -35,22 +35,24 @@ Create a new Worker project named `browser-worker` by running:
 
 ## 2. Install Puppeteer
 
-In your `browser-worker` directory, install Cloudflare’s [fork of Puppeteer](/browser-rendering/platform/puppeteer/):
+In your `browser-worker` directory, install Cloudflare's [fork of Puppeteer](/browser-rendering/platform/puppeteer/):
 
 ```sh
 npm install @cloudflare/puppeteer --save-dev
 ```
 
-## 3. Configure `wrangler.toml`
+## 3. Configure the `wrangler.toml / wrangler.json` file
 
-```
+<WranglerConfig>
+```toml
 name = "browser-worker"
 main = "src/index.ts"
 compatibility_date = "2023-03-14"
 compatibility_flags = [ "nodejs_compat" ]
 
 browser = { binding = "MYBROWSER" }
 ```
+</WranglerConfig>
 
 ## 4. Code
 

src/content/docs/browser-rendering/get-started/screenshots.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Render, TabItem, Tabs, PackageManagers } from "~/components";
+import { Render, TabItem, Tabs, PackageManagers, WranglerConfig } from "~/components";
 
 By following this guide, you will create a Worker that uses the Browser Rendering API to take screenshots from web pages. This is a common use case for browser automation.
 
@@ -56,17 +56,15 @@ npx wrangler kv:namespace create BROWSER_KV_DEMO --preview
 
 Take note of the IDs for the next step.
 
-## 4. Configure `wrangler.toml`
+## 4. Configure the `wrangler.toml / wrangler.json` file
 
-Configure your `browser-worker` project's [`wrangler.toml`](/workers/wrangler/configuration/) file by adding a browser [binding](/workers/runtime-apis/bindings/) and a [Node.js compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag). Bindings allow your Workers to interact with resources on the Cloudflare developer platform. Your browser `binding` name is set by you, this guide uses the name `MYBROWSER`. Browser bindings allow for communication between a Worker and a headless browser which allows you to do actions such as taking a screenshot, generating a PDF and more.
+Configure your `browser-worker` project's [`wrangler.toml / wrangler.json` file](/workers/wrangler/configuration/) by adding a browser [binding](/workers/runtime-apis/bindings/) and a [Node.js compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag). Bindings allow your Workers to interact with resources on the Cloudflare developer platform. Your browser `binding` name is set by you, this guide uses the name `MYBROWSER`. Browser bindings allow for communication between a Worker and a headless browser which allows you to do actions such as taking a screenshot, generating a PDF and more.
 
-Update your `wrangler.toml` configuration file with the Browser Rendering API binding and the KV namespaces you created:
-
-import { WranglerConfig } from "~/components";
+Update your `wrangler.toml / wrangler.json` file with the Browser Rendering API binding and the KV namespaces you created:
 
 <WranglerConfig>
 
-```toml
+```toml title="wrangler.toml"
 name = "browser-worker"
 main = "src/index.js"
 compatibility_date = "2023-03-14"

src/content/docs/browser-rendering/how-to/ai.mdx

@@ -4,9 +4,9 @@ sidebar:
   order: 2
 ---
 
-import { Aside } from "~/components";
+import { Aside, WranglerConfig } from "~/components";
 
-The ability to browse websites can be crucial when building workflows with AI. Here, we provide an example where we use Browser Rendering to visit 
+The ability to browse websites can be crucial when building workflows with AI. Here, we provide an example where we use Browser Rendering to visit
 `https://news.ycombinator.com/` and then, using a machine learning model available in [Workers AI](/workers-ai/), extract the first post as JSON with a specified schema.
 
 ## Prerequisites
@@ -30,16 +30,20 @@ npm i zod
 npm i zod-to-json-schema
 ```
 
-3. Activate the nodejs compatibility flag and add your Browser Rendering binding to your new `wrangler.toml` configuration:
+3. Activate the nodejs compatibility flag and add your Browser Rendering binding to your new Wrangler configuration:
 
+<WranglerConfig>
 ```toml
 compatibility_flags = [ "nodejs_compat" ]
 ```
+</WranglerConfig>
 
+<WranglerConfig>
 ```toml
 [browser]
 binding = "MY_BROWSER"
 ```
+</WranglerConfig>
 
 4.  In order to use [Workers AI](/workers-ai/), you need to get your [Account ID and API token](/workers-ai/get-started/rest-api/#1-get-api-token-and-account-id).
 Once you have those, create a [`.dev.vars`](/workers/configuration/environment-variables/#add-environment-variables-via-wrangler) file and set them there:

src/content/docs/browser-rendering/how-to/pdf-generation.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Aside } from "~/components";
+import { Aside, WranglerConfig } from "~/components";
 
 As seen in the [Getting Started guide](/browser-rendering/get-started/screenshots/), Browser Rendering can be used to generate screenshots for any given URL. Alongside screenshots, you can also generate full PDF documents for a given webpage, and can also provide the webpage markup and style ourselves.
 
@@ -23,11 +23,13 @@ npm create cloudflare@latest -- browser-worker
 npm install @cloudflare/puppeteer --save-dev
 ```
 
-3. Add your Browser Rendering binding to your new `wrangler.toml` configuration:
+3. Add your Browser Rendering binding to your new Wrangler configuration:
 
+<WranglerConfig>
 ```toml
 browser = { binding = "BROWSER" }
 ```
+</WranglerConfig>
 
 4. Replace the contents of `src/index.ts` (or `src/index.js` for JavaScript projects) with the following skeleton script:
 

src/content/docs/browser-rendering/platform/wrangler.mdx

@@ -19,7 +19,7 @@ To install Wrangler, refer to [Install and Update Wrangler](/workers/wrangler/in
 
 [Bindings](/workers/runtime-apis/bindings/) allow your Workers to interact with resources on the Cloudflare developer platform. A browser binding will provide your Worker with an authenticated endpoint to interact with a dedicated Chromium browser instance.
 
-To deploy a Browser Rendering Worker, you must declare a [browser binding](/workers/runtime-apis/bindings/) in your Worker's `wrangler.toml` configuration file.
+To deploy a Browser Rendering Worker, you must declare a [browser binding](/workers/runtime-apis/bindings/) in your Worker's Wrangler configuration file.
 
 <Render file="nodejs-compat-howto" product="workers" />