expect(received).toHaveLength(expected) Expected length: 2 Received length: 1 Received array: [{"rest": "PASS __tests__/bar.spec.js PASS __tests__/foo.spec.js", "summary": "Test Suites: 2 passed, 2 total Tests: 4 passed, 4 total Snapshots: 0 total Time: <<REPLACED>> Ran all test suites."}] at Object.toHaveLength (e2e/__tests__/watchModePatterns.test.ts:49:19)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

expect(received).toMatchSnapshot() Snapshot name: `can press "p" to filter by file name 1` - Snapshot - 39 + Received + 0 - <hideCursor> - <clearTerminal> - Pattern Mode Usage - › Press Esc to exit pattern mode. - › Press Enter to filter by a filenames regex pattern. - - <showCursor> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › - <saveCursorPosition> - <moveCursorToRow6Column12> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › b - <saveCursorPosition> - <moveCursorToRow6Column13> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › ba - <saveCursorPosition> - <moveCursorToRow6Column14> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › bar - <saveCursorPosition> - <moveCursorToRow6Column15> - <restoreCursorPosition> - - <moveCursorDownBy1Row> - <eraseScreenDown> - at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:48:18)

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

expect(received).toMatchSnapshot() Snapshot name: `can press "t" to filter by test name 1` - Snapshot - 25 + Received + 0 - <hideCursor> - <clearTerminal> - Pattern Mode Usage - › Press Esc to exit pattern mode. - › Press Enter to filter by a tests regex pattern. - - <showCursor> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › - <saveCursorPosition> - <moveCursorToRow6Column12> - <restoreCursorPosition> - <eraseLine> - <moveCursorToColumn1> - <eraseScreenDown> - pattern › 2 - <saveCursorPosition> - <moveCursorToRow6Column13> - <restoreCursorPosition> - - <moveCursorDownBy1Row> - <eraseScreenDown> - at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:67:18)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /home/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Node LTS on Ubuntu with coverage (3/4)

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

Ubuntu with shard 1/4 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Watch mode flows › Correctly passing test name pattern: undefined#L1

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

notify › does not report --notify flag: e2e/__tests__/detectOpenHandles.ts#L111

expect(received).toBe(expected) // Object.is equality Expected: "" Received: "Jest did not exit one second after the test run has completed.· 'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue." at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)

macOS with shard 2/3 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

ENOENT: no such file or directory, open '/tmp/jest-tmp/watch-test-fake.test.js' at Object.writeFileSync (packages/jest-core/src/__tests__/watchFileChanges.test.ts:55:8)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

ENOENT: no such file or directory, open '/tmp/jest-tmp/watch-test-fake.test.js' at Object.writeFileSync (packages/jest-core/src/__tests__/watchFileChanges.test.ts:55:8)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

ENOENT: no such file or directory, open '/tmp/jest-tmp/watch-test-fake.test.js' at Object.writeFileSync (packages/jest-core/src/__tests__/watchFileChanges.test.ts:55:8)

Ubuntu with shard 3/4 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testPathPatterns') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:159:34)

Watch mode flows › Correctly passing test name pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testNamePattern') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:175:33)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:191:11)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Watch mode flows › resolves relative to the package root: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:224:7)

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testPathPatterns') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:159:34)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testNamePattern') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:175:33)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:191:11)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:224:7)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Ubuntu with shard 3/4 / Node v18.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Ubuntu with shard 3/4 / Node v16.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Ubuntu with shard 3/4 / Node v20.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Ubuntu with shard 3/4 / Node v22.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Ubuntu with shard 3/4 / Node v21.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

ENOENT: no such file or directory, open '/var/folders/3m/p59k4qdj0f17st0gn2cmj3640000gn/T/jest-tmp/watch-test-fake.test.js' at Object.writeFileSync (packages/jest-core/src/__tests__/watchFileChanges.test.ts:55:8)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

macOS with shard 3/3 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "u" to update snapshots: e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50

expect(received).toMatchSnapshot(hint) Snapshot name: `can press "u" to update snapshots: test results 1` - Snapshot - 0 + Received + 1 @@ -14,7 +14,8 @@ | ^ at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35) › 1 snapshot failed. + A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them. Snapshot Summary › 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them." at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

Windows with shard 1/4 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

collects coverage only from multiple specified files: e2e/__tests__/coverageReport.test.ts#L66

expect(received).toMatchSnapshot() Snapshot name: `collects coverage only from multiple specified files 1` - Snapshot - 7 + Received + 0 - --------------|---------|----------|---------|---------|------------------- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s - --------------|---------|----------|---------|---------|------------------- - All files | 100 | 100 | 100 | 100 | - file.js | 100 | 100 | 100 | 100 | - otherFile.js | 100 | 100 | 100 | 100 | - --------------|---------|----------|---------|---------|------------------- at Object.toMatchSnapshot (e2e/__tests__/coverageReport.test.ts:66:18)

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

ENOENT: no such file or directory, open 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-tmp\watch-test-fake.test.js' at Object.writeFileSync (packages/jest-core/src/__tests__/watchFileChanges.test.ts:55:8)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Windows with shard 3/4 / Node LTS using jest-jasmine2

Final attempt failed. Child_process exited with error code 1

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L68

can press "t" to filter by test name: e2e/__tests__/watchModePatterns.test.ts#L67

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L49

can press "p" to filter by file name: e2e/__tests__/watchModePatterns.test.ts#L48

macOS with shard 2/3 / Node v16.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testPathPatterns') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:159:34)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

TypeError: Cannot set properties of undefined (setting 'testNamePattern') at Object.<anonymous> (packages/jest-core/src/__tests__/watch.test.js:175:33)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:191:11)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

TypeError: watch is not a function at Object.watch (packages/jest-core/src/__tests__/watch.test.js:224:7)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Windows with shard 3/4 / Node v20.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Windows with shard 3/4 / Node v16.x

Final attempt failed. Child_process exited with error code 1

macOS with shard 2/3 / Node v18.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Windows with shard 3/4 / Node v22.x

Final attempt failed. Child_process exited with error code 1

macOS with shard 2/3 / Node v21.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Windows with shard 3/4 / Node v18.x

Final attempt failed. Child_process exited with error code 1

macOS with shard 2/3 / Node v22.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

can pass projects or global config: packages/jest-haste-map/build/index.js#L246

Could not find test summary in the output. OUTPUT: FAIL project2/__tests__/file1.test.js ● Test suite failed to run The name `file1` was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or exclude files until there remains only one of these: * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project1\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project2\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project3\file1.js` (module) > 1 | const file1 = require('file1'); | ^ 2 | test('file1', () => {}); at ModuleMap._assertNoDuplicates (packages/jest-haste-map/build/index.js:246:11) at Object.<anonymous> (project2/__tests__/file1.test.js:1:31) FAIL project1/__tests__/file1.test.js ● Test suite failed to run The name `file1` was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or exclude files until there remains only one of these: * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project1\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project2\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project3\file1.js` (module) > 1 | const file1 = require('file1'); | ^ 2 | test('file1', () => {}); at Object.<anonymous> (project1/__tests__/file1.test.js:1:31) FAIL project3/__tests__/file1.test.js ● Test suite failed to run The name `file1` was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or exclude files until there remains only one of these: * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project1\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project2\file1.js` (module) * `C:\Users\runneradmin\AppData\Local\Temp\multi-project-runner-test\project3\file1.js` (module) > 1 | const file1 = require('file1'); | ^ 2 | test('file1', () => {}); at Object.<anonymous> (project3/__tests__/file1.test.js:1:31) node:events:497 throw er; // Unhandled 'error' event ^ Error: kill EPERM at ChildProcess.kill (node:internal/child_process:512:26) at listOnTimeout (node:internal/timers:573:17) at process.processTimers (node:internal/timers:514:7) Emitted 'error' event on ChildProcess instance at: at ChildProcess.kill (node:internal/child_process:512:12) [... lines matching original stack trace ...] at process.processTimers (node:internal/timers:514:7) { errno: -4048, code: 'EPERM', syscall: 'kill' } Node.js v21.7.3 at extractSummary (e2e/Utils.ts:245:11) at Object.<anonymous> (e2e/__tests__/multiProjectRunner.test.ts:89:24)

Windows with shard 3/4 / Node v21.x

Final attempt failed. Child_process exited with error code 1

macOS with shard 2/3 / Node v20.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

macOS with shard 3/3 / Node v18.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

macOS with shard 3/3 / Node v16.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

macOS with shard 3/3 / Node v21.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

macOS with shard 3/3 / Node v20.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows with changed files › should correct require new files without legacy cache: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: /Users/runner/work/jest/jest/node_modules/ansi-escapes/index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

macOS with shard 3/3 / Node v22.x

Final attempt failed. Child_process exited with error code 1

Watch mode flows › Correctly passing test path pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Correctly passing test name pattern: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest once by default and shows usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › Runs Jest in a non-interactive environment not showing usage: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › resolves relative to the package root: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows prompts for WatchPlugins in alphabetical order: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (without interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › shows update snapshot prompt (with interactive): undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to hook into JestHook: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Watch mode flows › allows WatchPlugins to override eligible internal plugins: undefined#L1

Jest encountered an unexpected token Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax. Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration. By default "node_modules" folder is ignored by transformers. Here's what you can do: • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it. • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config. • If you need a custom transformation specify a "transform" option in your config. • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option. You'll find more details and examples of these config options in the docs: https://jestjs.io/docs/configuration For information about custom transformations, see: https://jestjs.io/docs/code-transformation Details: D:\a\jest\jest\node_modules\ansi-escapes\index.js:1 ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export * from './base.js'; ^^^^^^ SyntaxError: Unexpected token 'export' at Runtime.createScriptFromCode (packages/jest-runtime/build/index.js:1316:14)

Node LTS on Ubuntu with coverage (4/4)

Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1

Node LTS on Ubuntu with coverage (1/4)

Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1

Node LTS on Ubuntu with coverage (1/4)