zoomdong

This commit **fixes a parsing issue** within **Turbopack's core path resolution** logic, specifically in `turbopack/crates/turbopack-core/src/resolve/parse.rs`. Previously, Windows absolute paths that utilized forward slashes, such as `C:/Users/demo/src/index.ts`, were not correctly identified as Windows paths. The `WINDOWS_PATH` regular expression has been updated to properly recognize these common path formats, ensuring **improved cross-platform compatibility** for Turbopack users on Windows. A new test case was also added to validate this corrected behavior, preventing future regressions in path interpretation.

This commit **adds support for the `verbatimModuleSyntax` option** to **Turbopack's TypeScript transform**, addressing a critical **compatibility issue** for projects using **React classic JSX transform**. Previously, the default TypeScript transform would remove `import React from 'react'`, causing runtime errors when JSX was converted to `React.createElement` calls. This **new capability** allows Turbopack to correctly preserve these essential imports, ensuring proper functioning for applications utilizing React 16+ with classic JSX. The change impacts the **`next-core`** and **`turbopack`** crates, specifically their handling of `tsconfig.json` options and the underlying SWC transformation logic.

This commit **fixes a critical bug in Turbopack's resolver** where **query parameters were incorrectly lost during alias resolution**. Specifically, the `resolve_import_map_result` function within `turbopack/crates/turbopack-core/src/resolve/mod.rs` has been updated to **correctly preserve these query parameters** and refine cycle detection logic during import map processing. This ensures that aliased imports containing resource queries are properly handled, preventing unexpected build failures and ensuring consistent module resolution behavior. New end-to-end tests have been added to validate this fix for both Turbopack and Webpack alias configurations, confirming the correct resolution of aliased paths with query parameters.

This commit introduces **support for configuring the `chunkLoadingGlobal` variable** within **Turbopack's browser runtime**, allowing users to specify a custom global variable name instead of the default `globalThis.TURBOPACK`. This **new capability** is crucial for preventing **variable collision issues** when multiple Turbopack-built applications, such as micro-frontends or iframe-based apps, coexist on the same page. The changes span the **`turbopack-browser`** crate for chunking context and content generation, and the **`turbopack-ecmascript-runtime`** for dynamic runtime code. This **feature addition** enhances Turbopack's flexibility and compatibility for complex deployment scenarios, validated by new snapshot tests.

This commit introduces a **new feature** to **Turbopack's module matching system**, enhancing its ability to resolve modules based on their resource queries. It adds a `ResourceQueryContains` variant to the `RuleCondition` enum, allowing rules to precisely match modules where the resource query string *contains* a specified substring. This is crucial for correctly processing imports like `import styles from './index.less?modules'`, ensuring that **CSS modules** and similar features are applied as intended. The change primarily affects the **`module_options` subsystem**, providing greater flexibility in defining module processing rules.

This commit **fixes a bug** in **Turbopack's webpack-loaders** where relative paths for custom loaders were not correctly resolved, leading to build failures. Previously, loaders specified with paths like `./test-file-loader.js` in `next.config.js` would fail to be found because the resolution context was incorrectly derived from the resource path. The fix modifies the `turbopack-node` crate to include the `contextDir` in the `paths` array used by `__turbopack_external_require__.resolve`. This ensures that **relative webpack loader paths** are properly located, improving the reliability of custom loader configurations within **Turbopack**.

This commit introduces a **bug fix** for **Turbopack's external module resolution**, specifically when `externalType` is set to `global` or `script`. Previously, modules like UMD packages without a `default` export were incorrectly wrapped, causing `esmImport` to return `undefined` when accessing `module["default"]`. The fix modifies `turbopack/crates/turbopack-ecmascript/src/references/external_module.rs` to use `TURBOPACK_EXPORT_VALUE` for these external types, ensuring `esmImport` correctly falls back to `interopEsm` for proper module interoperability. This change improves **Turbopack's compatibility** with diverse external module formats and is validated by new **Turbopack test cases** that verify correct global external value access.

This commit delivers a **bug fix** within the **Turbopack ECMAScript module**, specifically addressing the handling of **external script references**. It ensures that external script modules are correctly identified and configured as **async modules** in `turbopack-ecmascript/src/references/external_module.rs`. This correction is vital because these scripts often depend on asynchronous operations, such as the `loadurl` function, and their proper async classification is necessary to allow external imports to function as intended. This resolves an issue where external scripts were not correctly placed under async modules, preventing proper execution.

This commit **optimizes the collection of output assets** within the **`next-napi` crate**, specifically in the `output_assets_operation` function located in `project.rs`. It introduces a **performance refactoring** by replacing an inefficient manual loop that used `extend()` calls with a single, more idiomatic `flat_map().collect()` operation. This change aims to **reduce function call overhead and improve memory allocation efficiency** when gathering assets from multiple endpoints, potentially leading to faster build processes or development server startup times for Next.js applications utilizing the NAPI.

This commit introduces a **new feature** to the **`turbo-esregex`** crate, adding a `captures` method to the `EsRegex` struct. This method enables the extraction of matched groups from a string using the configured regular expression, enhancing the utility of `EsRegex` for advanced pattern matching. Specifically, it addresses the need for `EsRegex` to support capturing match strings from user-defined regex configurations in various scenarios. This improvement allows for more flexible and powerful string processing capabilities within **Turbopack**.

This commit introduces a **new `Script` external type** to **Turbopack**, mirroring Webpack's `externalsType: 'script'` behavior. This **new capability** allows developers to specify external modules using a `root@script_url` format, enabling **Turbopack** to generate runtime JavaScript code that loads the external package directly from the provided URL. The change impacts the **`turbopack-core` resolution logic** by extending the `ExternalType` enum, the **`turbopack-ecmascript` module for generating the necessary loading code**, and the main **`turbopack` crate's external handling** through updates to `externals_tracing_module_context` and `replace_external`. This enhancement provides greater flexibility for integrating external scripts and improves compatibility with existing Webpack configurations.

This commit introduces a **new capability** to **Turbopack** by adding support for a `global` external type, enabling modules to be treated as global variables rather than being bundled. This involves extending the `ExternalType` enum and its resolution logic within `turbopack-core`, and updating the `turbopack-ecmascript` crate to generate appropriate code for these global external modules via the `content` function. The main `turbopack` crate is also updated to integrate this new type into its external handling, tracing, and replacement functions. This enhancement provides greater flexibility in managing external dependencies, mirroring functionality found in other bundlers like Webpack's `externalsType: 'global'`.

This commit performs a **refactoring** within **Turbopack's core resolution logic** by **renaming a key field** in the `ResolveOptions` struct. The `plugins` field, which holds a list of resolution plugins, has been renamed to `after_resolve_plugins` to more accurately reflect their execution timing after the initial resolution step. This change affects the `turbopack-core` and `turbopack-resolve` crates, updating the struct definition in `turbopack-core/src/resolve/options.rs` and all points where these plugins are iterated or instantiated, such as in `handle_after_resolve_plugins` and `base_resolve_options`. The primary goal is to enhance code clarity and maintainability by providing a more semantically precise name for this collection of plugins, with no functional impact on the resolution process.