chore(deps): update dependency source-map to v0.7.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
source-map	0.7.3 -> 0.7.6
@types/source-map	0.5.0 -> 0.5.7

---

Release Notes

mozilla/source-map (source-map)

v0.7.6

Compare Source

• Bump package to 0.7.6 and remove publishConfig property in package.json (801be934007c3ed0ef66c620641b1668e92c891d)

v0.7.5

Compare Source

• #​364 -
  Pass through the implementation of more index map operations.
• #​362 -
  Remove the bundled dist/ directory?
• #​363 -
  Split up wasm loading based on compilation target.
• #​371 -
  Use WHATWG's URL to implement all of source-map's URL operations.
• #​378 -
  Fix typo
• #​384 -
  Add Mozilla Code of Conduct in
• #​402 -
  Remove unused fromVLQSigned function
• #​374 -
  Add lastGeneratedColumn to typing for MappingItem
• #​395 -
  addMapping(): ensure that originalLine and originalColumn are null when original argument was undefined/null
• #​394 -
  fix crash in url util function due to undefined root value
• #​393 -
  minor binary-search code/comment fixes
• #​407 -
  use Travis CI svg badge
• #​397 -
  add prettier task for standardized code formatting => easier cross-branch/fork code comparison and merging
• #​415 -
  Syntax highlight README HTML sample
• #​439 -
  Add function to SourceMapConsumer TS interface
• #​448 -
  Include types file extension in package.json
• #​464 -
  Require Node.js 12 or later & switch CI to GitHub Actions
• #​466 -
  Skip updating coveralls.io coverage
• #​465 -
  Update WASM binary and Land WASM rust sources in this repository
• #​463 -
  Update ESLint & Prettier to latest
• #​467 -
  Adopt & enforce the mozilla-central Prettier config
• #​468 -
  Simplify coverage tooling
• #​469 -
  Update to doctoc v2 & simplify call pattern
• #​470 -
  Filter out unnecessary rust tasks
• #​471 -
  Improve coverage
• #​472 -
  Include package-lock.json in repo
• #​473 -
  fix: convert result of allocate_mappings from signed to unsigned
• #​481 -
  Add support for the sourcemaps ignorelist
• #​485 -
  Remove .DS_Store
• #​488 -
  Fix reference to LICENSE file
• #​507 -
  Fix an off-by-1 error in section lookup
• #​505 -
  Add source map spec tests
• #​517 -
  Remove whatwg-url module

v0.7.4

Compare Source

• #​341 -
  Make async change. Fixes #​337.
• #​339 -
  Add option to initialize mappings wasm via ArrayBuffer
• #​347 -
  Add expected arguments to assert.throws calls
• #​352 -
  Update node version
• #​350 -
  Use top level context to determine node vs browser environment
• #​361 -
  Bump webpack-cli to v3.1
• #​456 -
  Regenerate dist due to running npm test

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[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 WARN cli npm v10.2.0 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.0 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"0.10.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"^0.7.2" from @angular/[email protected]
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"2.4.10" from the root project
npm ERR!   peer @angular/core@"2.4.10" from @angular/[email protected]
npm ERR!   node_modules/@angular/common
npm ERR!     @angular/common@"2.4.10" from the root project
npm ERR!     5 more (@angular/forms, @angular/platform-browser, ...)
npm ERR!   8 more (@angular/compiler, @angular/compiler-cli, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/zone.js
npm ERR!   peer zone.js@"^0.7.2" from @angular/[email protected]
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"2.4.10" from the root project
npm ERR!     peer @angular/core@"2.4.10" from @angular/[email protected]
npm ERR!     node_modules/@angular/common
npm ERR!       @angular/common@"2.4.10" from the root project
npm ERR!       5 more (@angular/forms, @angular/platform-browser, ...)
npm ERR!     8 more (@angular/compiler, @angular/compiler-cli, ...)
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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/124fb1/b2704f/cache/others/npm/_logs/2023-10-18T12_24_31_549Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/124fb1/b2704f/cache/others/npm/_logs/2023-10-18T12_24_31_549Z-debug-0.log

[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 warn cli npm v11.6.4 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular/[email protected]
npm error Found: [email protected]
npm error node_modules/zone.js
npm error   zone.js@"0.10.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer zone.js@"^0.7.2" from @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"2.4.10" from the root project
npm error   peer @angular/core@"2.4.10" from @angular/[email protected]
npm error   node_modules/@angular/common
npm error     @angular/common@"2.4.10" from the root project
npm error     5 more (@angular/forms, @angular/platform-browser, ...)
npm error   8 more (@angular/compiler, @angular/compiler-cli, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/zone.js
npm error   peer zone.js@"^0.7.2" from @angular/[email protected]
npm error   node_modules/@angular/core
npm error     @angular/core@"2.4.10" from the root project
npm error     peer @angular/core@"2.4.10" from @angular/[email protected]
npm error     node_modules/@angular/common
npm error       @angular/common@"2.4.10" from the root project
npm error       5 more (@angular/forms, @angular/platform-browser, ...)
npm error     8 more (@angular/compiler, @angular/compiler-cli, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-12-04T19_54_44_807Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-04T19_54_44_807Z-debug-0.log

[sonarqubecloud]

Quality Gate passed

Issues
132 New issues
0 Accepted issues

Measures
3 Security Hotspots
0.0% Coverage on New Code
0.2% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
134 New issues
0 Accepted issues

Measures
3 Security Hotspots
0.0% Coverage on New Code
0.2% Duplication on New Code

See analysis details on SonarQube Cloud