Step-by-step debugging gives the popular "Jest encountered an unexpected token"

[velganeshsubramanian]

I cloned the repo, opened in VS Code, and opened again with devcontainer, and ran npm install and npm test without any trouble. I created an action based on the template and couldn't do step-by-step debugging and wanted to check if it works in the template. It didn't. I didn't any configuration.

Running npx jest __tests__/main.test.ts -t "Sets the time output" in JavaScript Debug Terminal gives

Debugger attached.
Debugger attached.
 FAIL  __tests__/main.test.ts
  ● Test suite failed to run

    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:

    /workspaces/typescript-action/__tests__/main.test.ts:8
    import { afterEach, beforeEach, describe, expect, it, jest } from '@jest/globals';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1318:40)

----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |       0 |                   
 main.ts  |       0 |        0 |       0 |       0 | 10-25             
 wait.ts  |       0 |        0 |       0 |       0 | 8-11              
----------|---------|----------|---------|---------|-------------------
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.472 s
Ran all test suites matching __tests__/main.test.ts with tests matching "Sets the time output".
Waiting for the debugger to disconnect...
Waiting for the debugger to disconnect...

I am not sure which step from https://jestjs.io/docs/getting-started#using-typescript we have to adopt.

I am using Code 1.124.2. It gave errors in describe, beforeEach, etc. and the import statement in the test looks like

import {
  afterEach,
  beforeEach,
  describe,
  expect,
  it,
  jest
} from '@jest/globals'