Update dependency @size-limit/esbuild-why to ^11.1.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@size-limit/esbuild-why	^11.0.1 -> ^11.1.6

---

Release Notes

ai/size-limit (@​size-limit/esbuild-why)

v11.1.6

Compare Source

• Updated chokidar.
• Updated esbuild.
• Updated jiti.

v11.1.5

Compare Source

• Reduced dependencies (by @​ziebam).
• Updated esbuild.

v11.1.4

Compare Source

• Fixed types (by @​aryaemami59).

v11.1.3

Compare Source

• Updated esbuild.
• Updated CSS loaders for webpack.

v11.1.2

Compare Source

• Fixed CSS support in esbuild plugin (by @​just-boris).

v11.1.1

Compare Source

• Fixed Windows support (by @​aryaemami59).

v11.1.0

Compare Source

• Added TypeScript support for config (by @​aryaemami59).
• Fixed webpack-why regression (by @​hoo00nn).

v11.0.3

Compare Source

• Fixed .mjs config support (by Arya Emami).
• Updated esbuild.

v11.0.2

Compare Source

• Fixed require is not defined regression.
• Updated esbuild-visualizer.

---

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 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 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/size-limit
npm ERR!   dev size-limit@"^11.0.1" from the root project
npm ERR!   peer size-limit@"11.0.1" from @size-limit/[email protected]
npm ERR!   node_modules/@size-limit/esbuild
npm ERR!     dev @size-limit/esbuild@"^11.0.1" from the root project
npm ERR!   1 more (@size-limit/file)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @size-limit/esbuild-why@"^11.1.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/size-limit
npm ERR!   peer size-limit@"11.1.2" from @size-limit/[email protected]
npm ERR!   node_modules/@size-limit/esbuild-why
npm ERR!     dev @size-limit/esbuild-why@"^11.1.2" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-22T01_17_32_589Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-22T01_17_32_589Z-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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/size-limit
npm error   dev size-limit@"^11.0.1" from the root project
npm error   peer size-limit@"11.0.1" from @size-limit/[email protected]
npm error   node_modules/@size-limit/esbuild
npm error     dev @size-limit/esbuild@"^11.0.1" from the root project
npm error   1 more (@size-limit/file)
npm error
npm error Could not resolve dependency:
npm error dev @size-limit/esbuild-why@"^11.1.6" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/size-limit
npm error   peer size-limit@"11.1.6" from @size-limit/[email protected]
npm error   node_modules/@size-limit/esbuild-why
npm error     dev @size-limit/esbuild-why@"^11.1.6" from the root project
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 /tmp/renovate/cache/others/npm/_logs/2024-10-01T01_45_06_593Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-01T01_45_06_593Z-debug-0.log