fix: Update dependency ts-jest to v27.1.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-jest (source)	27.0.4 -> 27.1.5

---

Release Notes

kulshekhar/ts-jest (ts-jest)

v27.1.5

Compare Source

Bug Fixes

• transformers use Array.sort in hoisting transformer (#​3498) (e400a6e), fixes #​3476

v27.1.4

Compare Source

Bug Fixes

• compiler: revert #​3194 (#​3362) (2b7dffe), closes #​3272
• remove esbuild from peer dependency (#​3360) (8c8c1ca), closes #​3346
• support Babel config file with .cjs extension (#​3361) (5e5ac4a), closes #​3335

v27.1.3

Compare Source

Bug Fixes

• compiler: update memory cache for compiler using received file content (#​3194) (e4d9541)

v27.1.2

Compare Source

Bug Fixes

• stimulate esbuild type to avoid importing esbuild directly (#​3147) (9ace0a9)

v27.1.1

Compare Source

Bug Fixes

• bring back afterProcess hook (#​3132) (2b6b86e)
• make esbuild as optional peer dependency (#​3129) (20258de)

v27.1.0

Compare Source

Features

• allow subclasses to extend processAsync and getCacheKeyAsync (#​3047) (571a880)
• config: support custom AST transformers written in TypeScript (#​3063) (340a305), closes #​2831
• export ts-jest public apis from index.js (#​3080) (53175dd), closes #​3045

Code Refactoring

• utils: deprecate mocked util function (#​3102) (55e69f1)
• define clear type for compiler option (#​3087) (cc42daf)
• transformers: deprecate path-mapping AST transformer (#​3088) (d8f6b96)
• transformers: use ts factory API for hoisting AST transformer (#​3058) (a72f51d)

DEPRECATIONS

• transformers: path-mapping AST transformer is deprecated and will be removed in v28.0.0. One should use an alternative one like https://github.com/LeDDGroup/typescript-transform-paths instead.
• utils: mocked function is deprecated and will be removed in v28.0.0. The function has been integrated into jest-mock package as a part of Jest 27.4.0, see https://github.com/facebook/jest/pull/12089. One should use the one from Jest instead

27.0.7 (2021-10-16)

Bug Fixes

• correct lodash import (#​2978) (8b60679), closes #​2977

27.0.6 (2021-10-14)

Bug Fixes

• use specific lodash package instead of full package lodash (#​2959) (dc89fe5), closes #​2954

27.0.5 (2021-08-14)

Bug Fixes

• cli: add migration tsConfig option for ts-jest config options (#​2794) (781710b), closes #​2764
• cli: fix config:init genarate invalid type comment (#​2773) (ede8a20), closes #​2772
• config: handle ./ in tsconfig paths for pathsToModuleNameMapper (#​2797) (42ff5e4), closes #​2709

Code Refactoring

• use native Buffer.from and mkdird (#​2774) (4869660)

27.0.4 (2021-07-21)

Bug Fixes

• add @types/jest as optional peerDependencies to solve yarn 2 (#​2756) (5fbf43e)
• add babel-jest as optional peerDependencies to solve yarn 2 (#​2751) (8bede2e)
• config: include AST transformer's name and version into cache key (#​2755) (310fb9a), closes #​2753

Features

• link jest config types on npx ts-jest:init (#​2742) (f51ba05)
• set env var TS_JEST to allow detecting of ts-jest (#​2717) (56c137a), closes #​2716

27.0.3 (2021-06-06)

Bug Fixes

• revert exports field to support all node versions (#​2658) (132c8ba)

Features

• emit ESM codes if using ESM mode with Babel (#​2661) (9b55404), closes #​2650

27.0.2 (2021-05-30)

Bug Fixes

• compiler: add empty string file content to compiler cache (#​2633) (0feb556), closes #​2625
• config: exclude should only exclude files which match glob values (#​2637) (c5ce979), closes #​2634

27.0.1 (2021-05-26)

Bug Fixes

• cli: keep testMatch if old jest config contains it (#​2618) (c568f49), closes #​2616
• compiler: make sure isolatedModules: false use updated compiler options (#​2628) (348e30f), closes #​2629
• add missing export presets (#​2624) (0ea025e), closes #​2623

v27.0.7

Compare Source

Bug Fixes

• correct lodash import (#​2978) (8b60679), closes #​2977

v27.0.6

Compare Source

Bug Fixes

• use specific lodash package instead of full package lodash (#​2959) (dc89fe5), closes #​2954

v27.0.5

Compare Source

Bug Fixes

• cli: add migration tsConfig option for ts-jest config options (#​2794) (781710b), closes #​2764
• cli: fix config:init genarate invalid type comment (#​2773) (ede8a20), closes #​2772
• config: handle ./ in tsconfig paths for pathsToModuleNameMapper (#​2797) (42ff5e4), closes #​2709

Code Refactoring

• use native Buffer.from and mkdird (#​2774) (4869660)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR!   dev @types/jest@"26.0.24" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @types/jest@"^27.0.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"27.1.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @types/[email protected]
npm ERR! node_modules/@types/jest
npm ERR!   peerOptional @types/jest@"^27.0.0" from [email protected]
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"27.1.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-03-28T19_32_52_507Z-debug-0.log