Update dependency core-js to v3.42.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
core-js (source)	3.41.0 -> 3.42.0

---

Release Notes

zloirock/core-js (core-js)

v3.42.0

Compare Source

• Changes v3.41.0...v3.42.0 (142 commits)
• Map upsert proposal:
  • Moved to stage 2.7, April 2025 TC39 meeting
  • Validation order of WeakMap.prototype.getOrInsertComputed updated following tc39/proposal-upsert#79
  • Built-ins:
    • Map.prototype.getOrInsert
    • Map.prototype.getOrInsertComputed
    • WeakMap.prototype.getOrInsert
    • WeakMap.prototype.getOrInsertComputed
• Don't call well-known Symbol methods for RegExp on primitive values following tc39/ecma262#3009:
  • For avoid performance regression, temporarily, only in own core-js implementations
  • Built-ins:
    • String.prototype.matchAll
    • String.prototype.match
    • String.prototype.replaceAll
    • String.prototype.replace
    • String.prototype.search
    • String.prototype.split
• Added workaround for the Uint8Array.prototype.setFromBase64 bug in some of Linux builds of WebKit
• Implemented early-error iterator closing following tc39/ecma262#3467, including fix of a WebKit bug, in the following methods:
  • Iterator.prototype.drop
  • Iterator.prototype.every
  • Iterator.prototype.filter
  • Iterator.prototype.find
  • Iterator.prototype.flatMap
  • Iterator.prototype.forEach
  • Iterator.prototype.map
  • Iterator.prototype.reduce
  • Iterator.prototype.some
  • Iterator.prototype.take
• Fixed missing forced replacement of AsyncIterator helpers
• Added closing of sync iterator when async wrapper yields a rejection following tc39/ecma262#2600. Affected methods:
  • Array.fromAsync (due to the lack of async feature detection capability - temporarily, only in own core-js implementation)
  • AsyncIterator.from
  • Iterator.prototype.toAsync
• Added detection for throwing on undefined initial parameter in Iterator.prototype.reduce (see WebKit bug)
• core-js-compat and core-js-builder API:
  • Added 'intersect' support for targets.esmodules (Babel 7 behavior)
  • Fixed handling of targets.esmodules: true (Babel 7 behavior)
• Compat data improvements:
  • Explicit Resource Management features disabled (again) in V8 ~ Chromium 135 and re-added in 136
  • RegExp.escape marked as shipped from V8 ~ Chromium 136
  • Error.isError marked as shipped from FF138
  • Explicit Resource Management features re-enabled in Deno 2.2.10
  • Iterator helpers proposal features marked as supported from Deno 1.38.1 since it seems they were disabled in 1.38.0
  • Iterator.prototype.{ drop, reduce, take } methods marked as fixed in Bun 1.2.11
  • Added NodeJS 24.0 compat data mapping
  • Updated Electron 36 and added Electron 37 compat data mapping
  • Added Opera Android 88 and 89 compat data mapping
  • Added Oculus Quest Browser 37 compat data mapping

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​typescript-eslint/​parser@​6.21.0
	@​types/​jest@​29.5.13
	babel-plugin-transform-builtin-extend@​1.1.2
	@​typescript-eslint/​eslint-plugin@​6.21.0
	eslint-plugin-import@​2.31.0 ⏵ 2.29.1	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		[email protected] has Shell access. Module: child_process Location: Package overview Source: typescript/leap/package.json Source: typescript/leap/yarn.lock ℹ Read more on: This package | This alert | What is shell access? Next steps: 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 [email protected]. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		@nodelib/[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@nodelib/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		@nodelib/[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@nodelib/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] is a AI-detected potential code anomaly. Notes: The source code is intended to be a linting rule for JavaScript projects, but the use of _vm2['default'].runInNewContext() to execute comment contents dynamically is potentially dangerous. Confidence: 1.00 Severity: 0.60 Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Environment variable access. Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is environment variable access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Environment variable access. Env Vars: MINIMATCH_TESTING_PLATFORM Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is environment variable access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Environment variable access. Env Vars: key Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is environment variable access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Debug access. Module: module Location: Package overview Source: typescript/rna-transcription/package-lock.json Source: typescript/rna-transcription/package.json ℹ Read more on: This package | This alert | What is debug access? Next steps: 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 [email protected]. Suggestion: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Filesystem access. Module: fs Location: Package overview Source: typescript/leap/package.json Source: typescript/leap/yarn.lock ℹ Read more on: This package | This alert | What is filesystem access? Next steps: 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 [email protected]. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report