我的开发目录的路径在这里。

.
├── README.md
└── business
    ├── jest.config.ts
    ├── nodeLayer
    │   └── db
    │       ├── README.md
    │       ├── dist
    │       │   └── db
    │       │       ├── index.js
    │       │       └── index.js.map
    │       │  
    │       ├── package-lock.json
    │       ├── package.json
    │       ├── src
    │            └── index.ts
    │       
    └── hoge1
        └── src
            ├── README.md
            ├── app
            │   └── app.ts
            ├── jest.config.ts
            ├── package-lock.json
            ├── package.json
            └── tests
                └── unit
                    └── get.test.ts

当我使用Jest运行测试时，出现以下错误。

➤ npm run test

> [email protected] test
> npm run unit

> [email protected] unit
> NODE_OPTIONS=--experimental-vm-modules jest --config jest.config.ts

 FAIL  tests/unit/get.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:

    /xxxxxxxx/business/nodeLayer/db/dist/db/index.js:2
    import { createPool } from 'mysql2/promise';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       5 | import { ConnectionArguments, Db, SelectArguments } from '/opt/nodejs/dist/db';
       6 |
    >  7 | export const lambdaHandler = async (event: APIGatewayProxyEvent, context: Context): Promise<APIGatewayProxyResult> => {
         |              ^
       8 |     const client = new SecretsManagerClient({
       9 |         region: 'ap-northeast-1',
      10 |     });

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.<anonymous> (app/app.ts:7:14)
      at Object.<anonymous> (tests/unit/get.test.ts:4:15)

app.ts的导入在这里。由于我们正在导入Lambda层，因此将@ts-ignore注解掉，因为它将被检测为任何类型。

// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore
import { ConnectionArguments, Db, SelectArguments } from '/opt/nodejs/dist/db';

下面是jest.config.ts文件中的设置。

export default {
    preset: 'ts-jest',
    clearMocks: true,
    collectCoverage: true,
    coverageDirectory: 'coverage',
    coverageProvider: 'v8',
    testMatch: ['**/tests/unit/*.test.ts'],
    testPathIgnorePatterns: ['cf/.aws-sam/build'],
    moduleNameMapper: {
        '^/opt/nodejs/dist/db$': '<rootDir>/nodeLayer/db/dist/db',
    },
};

当我研究它时，我发现commonjs不能处理导入，所以我不得不改为ECM。
请在此处提供问题的解决方案。
如果你需要任何其他信息，就告诉我。