[wrangler] replace mentions of wrangler.json with wrangler.json(c) (#19764)

* update references of wrangler.json to wrangler.json(c)

* change to wrangler config file with link

* Update src/content/partials/workers/secrets-in-dev.mdx

---------

Co-authored-by: Jun Lee <[email protected]>

Author: emily-shen

src/components/WranglerConfig.astro

@@ -45,7 +45,7 @@ if (language === "toml") {
 ---
 
 <Tabs syncKey="wranglerConfig">
-	<TabItem label="wrangler.json" icon="seti:json">
+	<TabItem label="wrangler.jsonc" icon="seti:json">
 		<Code lang="jsonc" code={json} />
 	</TabItem>
 	<TabItem label="wrangler.toml" icon="setting">

src/content/changelogs-next/2025-01-26-worker-binding-methods.mdx

@@ -8,7 +8,7 @@ date: 2025-01-30T14:00:00Z
 
 We have released new [Workers bindings API methods](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
 
-To add an AI binding to your Worker, include the following in your `wrangler.toml` or `wrangler.json` file:
+To add an AI binding to your Worker, include the following in your [Wrangler configuration file](/workers/wrangler/configuration/):
 
 ![Add an AI binding to your Worker.](~/assets/images/ai-gateway/add-binding.png)
 

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 / wrangler.json` 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 configuration file](/workers/wrangler/configuration/) 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/agents/capabilities/mcp-server.mdx

@@ -99,7 +99,7 @@ This converts your Cloudflare Worker into an MCP server, enabling interactions w
 
 
 ### 5. Deploy the MCP Server
-Update your wrangler.toml with the appropriate configuration then deploy your Worker:
+Update your [Wrangler configuration file](/workers/wrangler/configuration/) with the appropriate configuration then deploy your Worker:
 ```bash
 wrangler deploy
 ```

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

@@ -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.json` configuration file.
+- A [Wrangler configuration file](/workers/wrangler/configuration/)
 
 Go to your application directory:
 
@@ -47,7 +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.json` file:
+To bind Workers AI to your Worker, add the following to the end of your [Wrangler configuration file](/workers/wrangler/configuration/):
 
 <WranglerConfig>
 
@@ -70,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 the `wrangler.toml / wrangler.json` file as the value for 'binding',
+	// If you set another name in the [Wrangler configuration file](/workers/wrangler/configuration/) as the value for 'binding',
 	// replace "AI" with the variable name you defined.
 	AI: Ai;
 }

src/content/docs/ai-gateway/integrations/worker-binding-methods.mdx

@@ -10,12 +10,11 @@ This guide provides an overview of how to use the latest Cloudflare Workers AI G
 
 ## Prerequisites
 
-- Ensure your Worker project is configured with an AI Gateway binding in `wrangler.json`.
 - Install and use the `@cloudflare/workers-types` library, version `4.20250124.3` or above.
 
 ## 1. Add an AI Binding to your Worker
 
-To connect your Worker to Workers AI, add the following to your `wrangler.toml` file:
+To connect your Worker to Workers AI, add the following to your [Wrangler configuration file](/workers/wrangler/configuration/):
 
 import { WranglerConfig } from "~/components";
 

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

@@ -13,7 +13,7 @@ import { DirectoryListing, WranglerConfig } from "~/components"
 
 ## 1. Name your dataset and add it to your Worker
 
-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.
+Add the following to your [Wrangler configuration file](/workers/wrangler/configuration/) 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

@@ -49,7 +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 the `wrangler.toml / wrangler.json` file:
+The account ID is set in the [Wrangler configuration file](/workers/wrangler/configuration/):
 
 <WranglerConfig>
 

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

@@ -71,9 +71,9 @@ After running the `list` command, you will see all bucket names, including the o
 
 ## 5. Configure your Wrangler configuration file
 
-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.
+Configure your `browser-worker` project's [Wrangler configuration 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 / wrangler.json` file with the Browser Rendering API binding, the R2 bucket you created and a Durable Object:
+Update your Wrangler configuration 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

@@ -41,7 +41,7 @@ In your `browser-worker` directory, install Cloudflare's [fork of Puppeteer](/br
 npm install @cloudflare/puppeteer --save-dev
 ```
 
-## 3. Configure the `wrangler.toml / wrangler.json` file
+## 3. Configure the [Wrangler configuration file](/workers/wrangler/configuration/)
 
 <WranglerConfig>
 ```toml