From f5d9e29becdb6fa1a7e6332b05803530563fd9cc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Somhairle=20MacLe=C3=B2id?= Date: Wed, 3 Sep 2025 17:19:53 +0100 Subject: [PATCH] Clarify JSON configuration file usage in docs Updated recommendation for configuration file format. --- src/content/docs/workers/wrangler/configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index cfc5f117256150d..86235b3f91f1f6a 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -18,7 +18,7 @@ Wrangler optionally uses a configuration file to customize the development and d As of Wrangler v3.91.0 Wrangler supports both JSON (`wrangler.json` or `wrangler.jsonc`) and TOML (`wrangler.toml`) for its configuration file. Prior to that version, only `wrangler.toml` was supported. -Cloudflare recommends using `wrangler.jsonc` for new projects. +Cloudflare recommends using `wrangler.jsonc` for new projects, and some newer Wrangler features will only be available to projects using a JSON config file. The format of Wrangler's configuration file is exactly the same across both languages, only the syntax differs.