[wrangler] Fix init --from-dash with Yarn Classic

[penalosa]

Fixes #8269.

When using Yarn Classic (v1.x), running wrangler init or wrangler init --from-dash would fail because Yarn Classic doesn't properly handle version specifiers with special characters like ^ in yarn create commands. Yarn would install the package correctly but then fail to find the binary because it would look for a path like .yarn/bin/create-cloudflare@^2.5.0 instead of .yarn/bin/create-cloudflare.

This fix removes the version specifier from the default C3 command entirely. Since C3 has had auto-update behavior for over two years, specifying a minimum version is no longer necessary and removing it resolves the Yarn Classic compatibility issue.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: This is a bug fix that restores expected behavior

---

[changeset-bot]

🦋 Changeset detected

Latest commit: de4cd06

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

[claude]

Claude finished @penalosa's task —— View job

---

Changeset Review

✅ All changesets look good

The changeset .changeset/fix-yarn-classic-init.md meets all requirements:

1. Version Type: ✅ Correctly marked as patch (bug fix)
2. Changelog Quality: ✅ Clear, descriptive explanation of the bug and the fix with good context
3. Markdown Headers: ✅ No h1/h2/h3 headers used
4. Analytics: ✅ No analytics changes
5. Experimental Features: ✅ Not applicable

The changeset provides excellent detail about both the problem (Yarn Classic's handling of version specifiers) and the solution (removing the version specifier since C3 has auto-update behavior).

---

[pkg-pr-new]

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: de4cd06

[penalosa]

@claude this is a pretty complex fix. Instead, I'd like to change the default C3 command in Wrangler to not include a version specifier. C3 has had auto-update behaviour for over two years now, and so specifying a version is no longer needed.

[claude]

Claude finished @penalosa's task —— View job

---

Simplifying C3 Command Approach ✅

Good point! Since C3 has auto-update behavior, we can simplify this significantly by just removing the version specifier entirely.

Todo List:

• Read current implementation to understand changes needed
• Simplify C3 command to remove version specifier
• Remove Yarn-specific helper functions
• Update tests to reflect new behavior
• Update changeset description
• Run checks and push changes

Changes implemented:

1. Removed version specifier from default C3 command: Changed "create cloudflare@^2.5.0" to "create cloudflare" in misc-variables.ts:37
2. Removed complex Yarn logic: Eliminated the isYarn() and sanitizeC3ArgsForYarn() functions from init.ts (22 lines removed)
3. Updated tests: Updated all test expectations to reflect the simpler command without version specifiers
4. Updated changeset: Revised the description to explain the simpler approach using C3's auto-update behavior

This approach is much cleaner than the original complex detection logic and resolves the Yarn Classic issue by simply removing the problematic version specifier entirely. Since C3 has had auto-update behavior for over two years, the version specifier was no longer necessary anyway.

Files modified:

• packages/workers-utils/src/environment-variables/misc-variables.ts
• packages/wrangler/src/init.ts
• packages/wrangler/src/__tests__/init.test.ts
• .changeset/fix-yarn-classic-init.md

✅ Changes have been committed and pushed to the PR branch.

---

[penalosa]

@claude fix CI checks

[claude]

Claude finished @penalosa's task —— View job

---

Fix CI Checks ✅

• Check current git status and recent changes
• Install dependencies and build packages
• Run code quality checks to identify failures
• Fix any linting/formatting issues
• Fix any type errors
• Fix any test failures
• Verify all checks pass
• Commit and push fixes

Issues found and fixed:

1. Documentation inconsistencies: Updated comments in factory.ts and misc-variables.ts to reflect the new default command "create cloudflare" instead of the old "create cloudflare@^2.5.0"

2. Formatting issue: Removed an extra blank line in init.ts

The core logic of your PR was correct - these were just documentation and formatting inconsistencies that would cause linting failures. The CI checks should now pass.

Changes committed and pushed:

• packages/workers-utils/src/environment-variables/factory.ts
• packages/workers-utils/src/environment-variables/misc-variables.ts
• packages/wrangler/src/init.ts

---

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional flags.