chore(deps): update dependency ts-jest to v29.2.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-jest (source)	29.1.1 -> 29.2.2

---

Release Notes

kulshekhar/ts-jest (ts-jest)

v29.2.2

Compare Source

v29.2.1

Compare Source

v29.2.0

Compare Source

Bug Fixes

• fix: don't show warning message with Node16/NodeNext (99c4f49), closes #​4266

Features

• feat(cli): allow migrating cjs presets to transform config (22fb027)
• feat(presets): add util functions to create ESM presets (06f78ed)
• feat(presets): add util functions to create CJS presets (f9cc3c0)

Code refactoring

• refactor: replace lodash deps with native js implementation (40f1708)
• refactor: use TsJestTransformerOptions type everywhere possibly (7d001be)
• refactor(cli): use new preset util functions to initialize test config (c2b56ca)
• refactor(presets): use create preset util functions for cjs presets (922d6d0)
• test: switch react-app to use Vite (827c8ad)

v29.1.5

Compare Source

Bug Fixes

• build(deps-dev): bump braces (5560334), (59026b4), (0d9e359)

v29.1.4

Compare Source

Bug Fixes

• fix(transformer): allow transforming of .cts/.mts extensions. (#​3996) (b8f6eaa), closes #​3996

Features

• feat: make cli generate esm config based on type: "module" (#​4210) (81a5f64), closes #​4210 #​4012

v29.1.3

Compare Source

Bug Fixes

• add @jest/transform as an optional peer dependency (0ba7f86)
• bring back Node 14 support (eda56a7)

Performance Improvements

• remove ts resolved module cache file (4c88da5)

v29.1.2

Compare Source

Bug Fixes

• calculated cache key based on supportsStaticESM (a5d6f2d)
• correct error handling in processAsync (e7be4bf), closes #​4207
• use Config.ProjectConfig (918312b), closes #​4028

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone America/New_York.

🚦 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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/http-proxy@1.18.1	network	0	232 kB	jcrugzz
npm/identity-obj-proxy@3.0.0	None	0	8.38 kB	keyanzhang
npm/jest-fetch-mock@3.0.3	network	0	104 kB	jefflau
npm/jest-mock-fetch@2.0.5	None	0	44.9 kB	knee-cola
npm/jsvectormap@1.5.3	None	0	398 kB	mustafaomar
npm/localforage@1.10.0	network	0	468 kB	tofumatt
npm/prop-types@15.8.1	environment	+1	119 kB	ljharb
npm/react@18.3.1	environment	0	318 kB	react-bot
npm/semver@7.6.2	None	0	95.4 kB	npm-cli-ops
npm/sharp@0.32.6	environment, filesystem, shell Transitive: network	+5	700 kB	lovell
npm/shx@0.3.4	None	+1	93.1 kB	nfischer
npm/skinview3d@3.0.1	None	0	2.37 MB	hacksore
npm/sort-by@1.2.0	None	0	11.1 kB	kvnneff
npm/svgmap@2.10.1	None	0	1.7 MB	stephanwagner
npm/three@0.158.0	None	0	31.3 MB	mrdoob
npm/typescript@5.4.5	None	0	32.4 MB	typescript-bot

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Install scripts	npm/core-js@3.37.1	Install script: postinstall Source: node -e "try{require('./postinstall')}catch(e){}"

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/core-js@3.37.1