Dario Piotrowicz

This commit **fixes** an issue within the **changesets validation** process by explicitly allowing **major version bumps for private packages**. The `validateChangesets` function in `tools/deployments/validate-changesets.ts` was updated to permit this, ensuring that internal modules can correctly signal breaking changes. A new test case in `tools/deployments/__tests__/validate-changesets.test.ts` was added to confirm this behavior. This change improves the flexibility and accuracy of the release workflow for **private package development**, preventing unnecessary restrictions on versioning.

This commit **refactors** the **`vitest-pool-workers`** package to enhance how `workerd` output is processed, switching from Miniflare's `handleRuntimeStdio` to the more advanced `handleStructuredLogs` option. This **enhancement** ensures that `workerd`'s structured log messages are correctly captured and routed to stdout or stderr based on their log level, including the ability to filter known internal messages. The change primarily affects the `packages/vitest-pool-workers/src/pool/index.ts` module, improving the fidelity and organization of test output. **New tests** in `packages/vitest-pool-workers/test/structured-logs.test.ts` validate this behavior, ensuring robust and accurate logging for users of the Vitest Workers pool.

This commit **refactors** and centralizes `gitignore` handling logic by introducing new, generic helper functions within the **`@cloudflare/cli` package**. It adds `maybeAppendWranglerToGitIgnore` and `maybeAppendWranglerToGitIgnoreLikeFile` to provide reusable functionality for appending entries to `.gitignore` or similar files. The **`create-cloudflare` (c3) project** is updated to utilize these new shared utilities, **removing its previously duplicated and inline `addWranglerToGitIgnore` logic**. This change improves code reusability, reduces maintenance overhead, and streamlines `gitignore` management across projects.

This commit performs a **code quality improvement** by **removing ESLint disabling comments** for the `no-restricted-imports` rule across the **`wrangler` end-to-end test suite**. To achieve this, various **test helper functions** such as `checkAssets`, `validateAssetUploadLogs`, `assertValidWorkerAiResponse`, and `assertInvalidWorkerAiResponse` were refactored to explicitly accept the `expect` object as an argument. This **refactoring** ensures proper import management within the `packages/wrangler/e2e` tests, enhancing their maintainability and reducing technical debt by enforcing stricter coding standards.

This commit performs a significant **code quality improvement** by removing numerous `no-restricted-imports` ESLint disabling comments from the **Wrangler test suite**. This **maintenance** task affects a wide array of test files within `packages/wrangler/src/__tests__`, spanning features such as `startDevWorker`, `cloudchamber`, `containers`, `r2`, `vectorize`, and `versions/secrets`. By eliminating these unnecessary suppressions, the codebase now adheres more strictly to established linting rules, enhancing consistency and maintainability. Some affected files also received minor adjustments to their Vitest imports, likely to conform to the now-enforced import restrictions. This effort streamlines the linting process and ensures better adherence to project coding standards across the test infrastructure.

This commit introduces **framework version validation** into `wrangler`'s **auto-configuration system**, adding a **new capability** to ensure that detected frameworks meet specified minimum and maximum version requirements. The `packages/wrangler/src/autoconfig` module is significantly updated, with the `runAutoConfig` function now incorporating checks via a new `validateFrameworkVersion` method on the base `Framework` class. This required **refactoring** individual framework definitions to expose their package versions and extensive **testing** of the new validation logic. This enhancement improves the reliability of auto-configuration by preventing `wrangler` from attempting to configure unsupported framework versions, leading to a more robust and predictable deployment experience.

This commit **improves error handling** within **Wrangler's asset management** by explicitly validating the provided asset directory path. The `getAssetsOptions` function now checks if the path specified via the `--assets` flag or configuration points to a directory, rather than a file. This **bug fix** and **user experience improvement** ensures that users receive a **more descriptive error message** when misconfiguring the asset path. This change affects both the `deploy` and `dev` commands, providing clearer feedback and is thoroughly covered by new **tests**.

This commit introduces a **new `@cloudflare/codemod` package** to centralize and **deduplicate codemod logic** previously shared between `create-cloudflare` (C3) and `wrangler`'s autoconfig features. This significant **refactoring** effort moves core utility functions like `parseFile`, `transformFile`, and `mergeObjectProperties` into the new package, improving code reusability and maintainability across the monorepo. As a result, both **`create-cloudflare` and `wrangler` now consume these utilities from the dedicated package**, streamlining future development and ensuring consistent application of codemod transformations. The new package also includes its own development and testing infrastructure, enhancing the overall developer experience for codemod creation.

This commit **refactors and migrates core command execution and package management utilities** (`runCommand`, `quoteShellArgs`, `installPackages`, `installWrangler`) from the `c3-vendor` module within `create-cloudflare` to the shared **`@cloudflare/cli`** package. This change centralizes common logic, improving reusability and maintainability for these critical CLI operations. Consequently, **`create-cloudflare` and `wrangler` have been updated to import these functions from their new location**, with old helper files in `create-cloudflare` being removed. New unit tests have been added for the moved functionality in `@cloudflare/cli`, ensuring continued reliability. This graduation establishes `@cloudflare/cli` as the canonical home for these shared utilities, streamlining development across Cloudflare's CLI tools.

This commit significantly **enhances the autoconfig framework detection logic** within **Wrangler**, introducing **new capabilities** for identifying project types. It now accurately detects various frameworks like static and Astro, different package managers (npm, pnpm, yarn, bun), and Cloudflare Pages projects based on configuration. A notable improvement is the **suppression of lock file warnings for static projects** during autoconfiguration, alongside robust error handling for scenarios where multiple frameworks are detected, particularly in CI environments. This comprehensive update, supported by extensive new test cases, ensures more reliable and precise project setup for users by improving the `autoconfig` subsystem.

This commit introduces a **bug fix** for **Wrangler's autoconfiguration** process, specifically addressing an issue where projects using both **Waku** and **Hono** frameworks would incorrectly report multiple frameworks. The fix modifies the `findDetectedFramework` function within `packages/wrangler/src/autoconfig/details.ts` to prioritize `waku` detection and filter out `hono` in such scenarios. This prevents erroneous "multiple frameworks found" errors, ensuring **Wrangler's autoconfiguration** works correctly for **Waku** projects that also include **Hono**. The change improves the robustness of framework detection for these specific project setups.

This commit performs a **documentation update** to reflect a change in the project's code formatting tool. It modifies `AGENTS.md` and `packages/create-cloudflare/AGENTS.md` to replace references to Prettier with `oxfmt`. This **maintenance** task ensures that the **developer guidelines** are accurate, informing contributors about the current standard for code formatting. The update improves the **onboarding experience** for new developers by providing correct information on required tooling.

This commit **updates the documentation** for **Wrangler**, specifically within the **Workers** section, to include details for two critical system environment variables. It **adds comprehensive information** regarding `CLOUDFLARE_ACCESS_CLIENT_ID` and `CLOUDFLARE_ACCESS_CLIENT_SECRET`, which are essential for configuring **Cloudflare Access** client credentials. This **documentation enhancement** improves user understanding and ease of setup for developers utilizing these environment variables. The change primarily affects the `src/content/docs/workers/wrangler/system-environment-variables.mdx` file, ensuring that users have complete and accurate reference material.

This commit introduces a **significant user experience improvement** by enhancing the error messages displayed when **Wrangler's bundling process** encounters **unresolved modules**. It implements a **fix** that intelligently rewrites `esbuild`'s output, replacing generic "mark as external" suggestions with specific, actionable advice to use the `alias` configuration for non-Node modules. This change, integrated into the `bundleWorker` function via the new `rewriteUnresolvedModuleBuildFailure` function, ensures developers receive clearer guidance, reducing friction and debugging time. New test cases have been added to verify that these improved messages correctly recommend `alias` for user modules but not for Node.js built-ins, ensuring accurate and helpful feedback.

This commit introduces **backward-compatible autoconfiguration support** for **Astro projects** within the **Wrangler CLI**. It implements a **new feature** that allows Wrangler to automatically detect and configure projects using both Astro v5 and Astro v4. The changes in `packages/wrangler/src/autoconfig/frameworks/astro.ts` include logic for `validateMinimumAstroVersion`, `findAstroConfigFile`, and `updateAstroConfig`, ensuring seamless setup and handling of legacy configurations. This enhancement significantly improves the developer experience by streamlining the integration of Astro applications with Wrangler, regardless of their specific Astro version.

This commit **updates the Wrangler documentation** by adding a new section to `src/content/docs/workers/wrangler/configuration.mdx`. The new content specifically addresses common **bundling issues** that users might encounter when utilizing **module aliasing** within their Wrangler configurations. This **documentation enhancement** provides potential solutions, aiming to improve the developer experience and help users troubleshoot related problems more effectively.

This commit **fixes a bug** in **Wrangler's `InspectorProxyWorker.ts`** that caused execution to freeze when a `debugger` statement was encountered without DevTools being attached. The fix modifies the debugger initialization logic, specifically within `_initialiseRuntime` and `_handleNewDevToolsConnection`, to conditionally enable the `Debugger.enable` protocol method. It also adds logic to disable the debugger when DevTools disconnects, preventing further hangs. This **improves the developer experience** by ensuring that `debugger` statements only pause execution when an active DevTools session is present, preventing unexpected hangs during development.

This commit **fixes a critical crash** within the **Vite Cloudflare plugin** that occurred when Hot Module Replacement (HMR) events were dispatched by plugins before the WebSocket connection was fully initialized. It introduces a **buffering mechanism** in `packages/vite-plugin-cloudflare/src/cloudflare-environment.ts` to safely queue these early events, ensuring they are processed once the WebSocket is ready. This **enhances the stability and reliability** of the HMR system, preventing runtime errors and improving the developer experience for `vite-plugin-cloudflare` users. The `CloudflareDevEnvironment`'s `send` and `setWebSocket` methods, along with the `WebSocketContainer` interface, are updated to support this change, and new test cases were added to validate the fix.

This commit delivers a **bug fix** for the **`wrangler` package's autoconfig feature**, addressing an issue where package installation consistently failed when executed at the root of a workspace. The solution involves introducing an `isWorkspaceRoot` flag, which is now accurately detected by `detectFramework` and passed through the autoconfig process to various framework configurations (e.g., Angular, Nuxt, SvelteKit). The core package installation utilities, specifically `installPackages` and `installWrangler` in `packages/wrangler/src/autoconfig/c3-vendor/packages.ts`, have been updated to accept and utilize this flag, enabling them to invoke package managers like pnpm and yarn with the appropriate workspace-aware commands. This ensures that autoconfig can successfully install dependencies for projects located within a monorepo's root, significantly improving the developer experience for workspace users.

This commit **fixes** an issue within the **`wrangler` package's asset deployment** where a `null` response from the assets upload session would result in an unclear error. The `syncAssets` function in `packages/wrangler/src/assets.ts` now explicitly checks for this `null` response and throws a **more descriptive error**, significantly improving user feedback during asset deployment failures. A new test case in `packages/wrangler/src/__tests__/deploy/assets.test.ts` has been added to validate this enhanced error handling. This **bug fix** ensures users receive actionable information when asset uploads encounter unexpected server responses.