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.5 -> 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)

---

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 these updates 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/@babel/helper-plugin-utils@7.10.4	None	0	4.05 kB	jlhwung
npm/@types/babel__traverse@7.0.13	None	0	42.5 kB	types
npm/@types/istanbul-lib-coverage@2.0.3	None	0	5.91 kB	types
npm/chalk@4.1.0	None	+4	66.5 kB	sindresorhus
npm/debug@4.1.1	environment	+1	88.3 kB	qix
npm/glob@7.1.6	filesystem Transitive: environment	+10	144 kB	isaacs
npm/kind-of@6.0.3	None	0	22.8 kB	doowb
npm/mem@9.0.2	None	+3	37.4 kB	sindresorhus
npm/ts-jest@29.2.1	Transitive: environment, eval, filesystem, network, shell, unsafe	+79	3.59 MB	anhpnnd, kul, tsjest
npm/tslint@6.1.3	filesystem Transitive: environment, eval, shell	+21	3.66 MB	palantir

🚮 Removed packages: npm/@babel/cli@7.24.7, npm/@babel/core@7.24.7, npm/@types/babel__traverse@7.14.2, npm/glob@7.2.0, npm/ts-jest@29.1.5, npm/tslint@5.20.1

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	Source	CI
Filesystem access	npm/filelist@1.0.4	Module: fs Location: Package overview	typescript/simple-cipher/package.json	🚫
Mild CVE	npm/debug@4.1.1	CVE: GHSA-gxpj-cx7g-858c Regular Expression Denial of Service in debug (LOW) Affected versions: >= 4.0.0, < 4.3.1 Patched version: 4.3.1	Source	🚫
Deprecated	npm/debug@4.1.1	Reason: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/ReDos Vulnerability Regression Visibility Notice debug-js/debug#797)	Source	🚫
Deprecated	npm/tslint@6.1.3	Reason: TSLint has been deprecated in favor of ESLint. Please see https://github.com/Roadmap: TSLint -> ESLint palantir/tslint#4534 for more information.	typescript/simple-cipher/package.json	🚫
Uses eval	npm/ejs@3.1.10	Eval Type: Function Location: Package overview	typescript/simple-cipher/package.json	🚫
Uses eval	npm/ejs@3.1.10	Eval Type: Function Location: Package overview	typescript/simple-cipher/package.json	🚫
Filesystem access	npm/ejs@3.1.10	Module: fs Location: Package overview	typescript/simple-cipher/package.json	🚫
Shell access	npm/jake@10.9.1	Module: child_process Location: Package overview	typescript/simple-cipher/package.json	🚫
Filesystem access	npm/jake@10.9.1	Module: fs Location: Package overview	typescript/simple-cipher/package.json	🚫
Environment variable access	npm/jake@10.9.1	Env Vars: Location: Package overview	typescript/simple-cipher/package.json	🚫

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is a mild CVE?

Contains a low severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

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/filelist@1.0.4
• @SocketSecurity ignore npm/debug@4.1.1
• @SocketSecurity ignore npm/tslint@6.1.3
• @SocketSecurity ignore npm/ejs@3.1.10
• @SocketSecurity ignore npm/jake@10.9.1