update snapshots

turbopack/crates/turbopack-tests/tests/execution/turbopack/async-modules/export-all/issues/unexpected export __star__-9b505f.txt

@@ -0,0 +1,3 @@
+warning - [analysis] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/async-modules/export-all/input/exports.js  unexpected export *
+  export * used with module [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/async-modules/export-all/input/exports.js [test] (ecmascript) which is a CommonJS module with exports only available at runtime
+  List all export names manually (`export { a, b, c } from "...") or rewrite the module to ESM, to avoid the additional runtime code.`

turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/issues/__l___Module not found____c__ Can't resolve '__c_.-8f66b2.txt → turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/issues/__l___Module not found____c__ Can't resolve '__c_.-c64628.txt

@@ -1,4 +1,4 @@
-error - [resolve] [project]/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js  /crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js:4:4  Module not found: Can't resolve './not-existing-file'
+error - [resolve] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js  /turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js:4:4  Module not found: Can't resolve './not-existing-file'
 
        1 | it("importing a not existing file should throw", () => {
        2 |   // This is a check to make sure that the following tests would fail if they require("fail")
@@ -15,6 +15,6 @@ error - [resolve] [project]/crates/turbopack-tests/tests/execution/turbopack/bas
 
   | It was not possible to find the requested file.
   | Parsed request as written in source code: relative "./not-existing-file"
-  | Path where resolving has started: [project]/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js
+  | Path where resolving has started: [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/comptime/input/index.js
   | Type of request: commonjs request
   |

turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/error/issues/Reading source code for parsing failed-ae17dd.txt → turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/error/issues/Reading source code for parsing failed-073388.txt

@@ -1,4 +1,4 @@
-error - [load] [project]/crates/turbopack-tests/tests/execution/turbopack/basic/error/input/broken.js  Reading source code for parsing failed
+error - [load] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/error/input/broken.js  Reading source code for parsing failed
   An unexpected error happened while trying to read the source code to parse: failed to convert rope into string
 
   Caused by:

turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/issues/Specified module format (CommonJs) is not matching-bae6b2.txt → turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/issues/Specified module format (CommonJs) is not matching-63a9f9.txt

@@ -1,4 +1,4 @@
-error - [analysis] [project]/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/input/node_modules/esm-package/invalid-exports.cjs  Specified module format (CommonJs) is not matching the module format of the source code (EcmaScript Modules)
+error - [analysis] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/input/node_modules/esm-package/invalid-exports.cjs  Specified module format (CommonJs) is not matching the module format of the source code (EcmaScript Modules)
   The CommonJs module format was specified in the package.json that is affecting this source file or by using an special extension, but Ecmascript import/export syntax is used in the source code.
   The module was automatically converted to an EcmaScript module, but that is in conflict with the specified module format. Either change the "type" field in the package.json or replace EcmaScript import/export syntax with CommonJs syntas in the source file.
   In some cases EcmaScript import/export syntax is added by an transform and isn't actually part of the source code. In these cases revisit transformation options to inject the correct syntax.

turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/issues/Specified module format (EcmaScript Modules) is no-5759f6.txt → turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/issues/Specified module format (EcmaScript Modules) is no-9d7f7e.txt

@@ -1,3 +1,3 @@
-warning - [analysis] [project]/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/input/node_modules/esm-package/invalid-exports.js  Specified module format (EcmaScript Modules) is not matching the module format of the source code (CommonJs)
+warning - [analysis] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/input/node_modules/esm-package/invalid-exports.js  Specified module format (EcmaScript Modules) is not matching the module format of the source code (CommonJs)
   The EcmaScript module format was specified in the package.json that is affecting this source file or by using an special extension, but it looks like that CommonJs syntax is used in the source code.
   Exports made by CommonJs syntax will lead to a runtime error, since the module is in EcmaScript mode. Either change the "type" field in the package.json or replace CommonJs syntax with EcmaScript import/export syntax in the source file.