feat: allow `wrangler types` to run without config file #11247

devin-ai-integration · 2025-11-12T12:43:20Z

This PR allows the wrangler types command to run without requiring a Wrangler config file, addressing a common pain point for developers who want to generate runtime types without a full project setup.

Changes

Added two new command-line arguments:

--compatibility-date: Specifies the compatibility date for runtime types (defaults to the latest date supported by the installed workerd)
--compatibility-flags: Specifies compatibility flags for runtime types

When no config file is detected:

The command will automatically use the latest workerd compatibility date if --compatibility-date is not provided
--include-env is automatically set to false (only runtime types are generated, not project-specific environment types)
Users can still provide compatibility settings via command-line arguments

Key Implementation Details

Config file detection: The handler now wraps config reading in a try-catch block. If no config is explicitly specified via -c, missing config files are treated as "no config" rather than an error.
Fallback chain: For compatibility settings, the code follows this priority:
- Command-line arguments (--compatibility-date, --compatibility-flags)
- Config file settings (if config exists)
- Default workerd compatibility date (if no config and no args)
Type safety: Added proper handling for config being undefined throughout the handler using optional chaining.
Backward compatibility: When a user explicitly specifies a config file with -c that doesn't exist, the command still errors as before.

Testing

Added 4 new test cases covering:

Generating runtime types without config when --compatibility-date is provided
Using default workerd compatibility date when no config and no args
Supporting --compatibility-flags argument without config
Verifying includeEnv is set to false when no config exists

All 49 existing tests continue to pass.

Areas for Review

⚠️ Important areas to review:

Type coercion on line 247-248 and 293-295: Using .map(String) to convert yargs' (string | number)[] to string[]. This is duplicated in two places - consider if this should be extracted to a helper.
Behavior change for configs without compatibility_date: Previously this would error in generateRuntimeTypes. Now it falls back to the default workerd date with a warning (lines 251-261). This is a breaking change that should be documented.
Config detection logic (lines 137-159): Verify the logic correctly distinguishes between "no config file found" vs "user explicitly specified a config file that doesn't exist".
Optional chaining throughout: Ensure all code paths properly handle config being undefined, especially in generateEnvTypes and when accessing config.configPath.

Link to Devin run: https://app.devin.ai/sessions/d05913dfe4fc454cbcd10f3734baeb68
Requested by: [email protected]

Tests
- Tests included
Public documentation
- Documentation not necessary because: This is a new feature that will be documented in the changeset and users can discover via wrangler types --help
Wrangler V3 Backport
- Not necessary because: This is a new feature (minor version bump)

Add --compatibility-date and --compatibility-flags arguments to the wrangler types command, making the config file optional. When no config file is detected, the command will: - Use the latest workerd compatibility date by default - Set includeEnv to false (only generate runtime types) - Accept compatibility settings via command-line arguments Co-Authored-By: [email protected] <[email protected]>

devin-ai-integration · 2025-11-12T12:43:24Z

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

Disable automatic comment and CI monitoring

changeset-bot · 2025-11-12T12:43:24Z

🦋 Changeset detected

Latest commit: 36e79e8

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

pkg-pr-new · 2025-11-12T12:45:56Z

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11247

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11247

miniflare

npm i https://pkg.pr.new/miniflare@11247

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11247

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11247

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11247

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11247

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11247

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11247

wrangler

npm i https://pkg.pr.new/wrangler@11247

commit: 36e79e8

Co-Authored-By: [email protected] <[email protected]>

penalosa · 2025-11-12T21:56:06Z

packages/wrangler/src/type-generation/index.ts

+			// Get the maximum compatibility date supported by the installed workerd
+			const miniflareEntry = require.resolve("miniflare");
+			const miniflareRequire = module.createRequire(miniflareEntry);
+			const miniflareWorkerd = miniflareRequire("workerd") as {
+				compatibilityDate: string;
+			};
+			args.compatibilityDate = miniflareWorkerd.compatibilityDate;
+			logger.log(
+				`No config file detected. Using the installed Workers runtime's latest supported date: ${args.compatibilityDate}\n`
+			);
+		}


There's a utility function for this called getDevCompatibilityDate(). Use that instead

Done! Replaced the manual workerd resolution with getDevCompatibilityDate() in both locations (lines 149-154 and 224-228).

penalosa · 2025-11-12T21:58:10Z

packages/wrangler/src/type-generation/index.ts

+		let config: Config | undefined;
 		const secondaryConfigs: Config[] = [];
-		if (Array.isArray(args.config)) {
-			config = readConfig({ ...args, config: args.config[0] });
-			for (const configPath of args.config.slice(1)) {
-				secondaryConfigs.push(readConfig({ config: configPath }));
+		let hasConfigFile = false;
+
+		try {
+			if (Array.isArray(args.config)) {
+				config = readConfig({ ...args, config: args.config[0] });
+				for (const configPath of args.config.slice(1)) {
+					secondaryConfigs.push(readConfig({ config: configPath }));
+				}
+			} else {
+				config = readConfig(args);
 			}
-		} else {
-			config = readConfig(args);
+
+			if (
+				config.configPath &&
+				fs.existsSync(config.configPath) &&
+				!fs.statSync(config.configPath).isDirectory()
+			) {
+				hasConfigFile = true;
+			}
+		} catch (error) {
+			if (args.config) {
+				throw error;
+			}
+			config = undefined;


This is all a bit overkill. readConfig() won't throw if no config file exists

Done! Simplified the config reading logic by removing the try-catch block and fs checks. Now using const hasConfigFile = Boolean(config.configPath) to detect if a config file exists (lines 137-146).

penalosa · 2025-11-12T21:59:05Z

packages/wrangler/src/type-generation/index.ts

+			let compatibilityDate =
+				args.compatibilityDate ?? config?.compatibility_date;
+			const compatibilityFlags =
+				args.compatibilityFlags?.map(String) ??


This shouldn't need a .map(String)

Done! Removed .map(String) and used a type assertion instead: compatibilityFlags as string[] (lines 229-230 and 235).

penalosa · 2025-11-12T21:59:26Z

packages/wrangler/src/type-generation/index.ts

+			if (!compatibilityDate) {
+				const miniflareEntry = require.resolve("miniflare");
+				const miniflareRequire = module.createRequire(miniflareEntry);
+				const miniflareWorkerd = miniflareRequire("workerd") as {
+					compatibilityDate: string;
+				};
+				compatibilityDate = miniflareWorkerd.compatibilityDate;
+				if (hasConfigFile) {
+					logger.warn(
+						`No compatibility_date was specified. Using the installed Workers runtime's latest supported date: ${compatibilityDate}`
+					);
+				}
+			}


At this point there should always be a compat date. Remove this check

Done! Removed the entire if (!compatibilityDate) check since getDevCompatibilityDate() now guarantees a compatibility date is always returned (lines 224-228).

- Use getDevCompatibilityDate() utility instead of manual workerd resolution - Simplify config reading by removing unnecessary try-catch and fs checks - Remove .map(String) from compatibilityFlags (use type assertion instead) - Remove redundant if (!compatibilityDate) check - Remove unused node:module import Co-Authored-By: [email protected] <[email protected]>

- Add type assertion to handle yargs array type (string | number)[] - Ensure compatibilityFlags is typed as string[] for getNodeCompat() - Provide default empty array when compatibilityFlags is undefined Co-Authored-By: [email protected] <[email protected]>

workers-devprod added this to workers-sdk Nov 12, 2025

github-project-automation bot moved this to Untriaged in workers-sdk Nov 12, 2025

devin-ai-integration bot and others added 2 commits November 12, 2025 12:50

ci: retry tests

14f3ad1

Co-Authored-By: [email protected] <[email protected]>

ci: retry Windows tests

026a53b

Co-Authored-By: [email protected] <[email protected]>

penalosa reviewed Nov 12, 2025

View reviewed changes

devin-ai-integration bot and others added 2 commits November 12, 2025 22:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: allow `wrangler types` to run without config file #11247

feat: allow `wrangler types` to run without config file #11247

Uh oh!

devin-ai-integration bot commented Nov 12, 2025

Uh oh!

devin-ai-integration bot commented Nov 12, 2025

Uh oh!

changeset-bot bot commented Nov 12, 2025 •

edited

Loading

Uh oh!

pkg-pr-new bot commented Nov 12, 2025 •

edited

Loading

Uh oh!

penalosa Nov 12, 2025

Uh oh!

devin-ai-integration bot Nov 12, 2025

Uh oh!

penalosa Nov 12, 2025

Uh oh!

devin-ai-integration bot Nov 12, 2025

Uh oh!

penalosa Nov 12, 2025

Uh oh!

devin-ai-integration bot Nov 12, 2025

Uh oh!

penalosa Nov 12, 2025

Uh oh!

devin-ai-integration bot Nov 12, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

feat: allow wrangler types to run without config file #11247

Are you sure you want to change the base?

feat: allow wrangler types to run without config file #11247

Uh oh!

Conversation

devin-ai-integration bot commented Nov 12, 2025

Changes

Key Implementation Details

Testing

Areas for Review

Uh oh!

devin-ai-integration bot commented Nov 12, 2025

🤖 Devin AI Engineer

Uh oh!

changeset-bot bot commented Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

pkg-pr-new bot commented Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

penalosa Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration bot Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

penalosa Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration bot Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

penalosa Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration bot Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

penalosa Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration bot Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

feat: allow `wrangler types` to run without config file #11247

feat: allow `wrangler types` to run without config file #11247

changeset-bot bot commented Nov 12, 2025 •

edited

Loading

pkg-pr-new bot commented Nov 12, 2025 •

edited

Loading