chore(package): Update dependency rollup-plugin-svelte to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup-plugin-svelte	6.1.1 -> 7.1.4

---

Release Notes

sveltejs/rollup-plugin-svelte

v7.1.4

Compare Source

• Forward options to this.resolve (#​208)

v7.1.3

Compare Source

• Warn if svelte export condition is missing (#​206)

v7.1.2

Compare Source

• Fix package resolution (#​205)

v7.1.0

Compare Source

• Preprocessor sourcemap support (#​157)

v7.0.0

Compare Source

• New minimum version requirements (#​138, #​142):
  • Rollup 2+
  • Svelte 3.5+ (Svelte 2 is no longer supported)
  • Node 10+
• Breaking: Offload CSS handling to Rollup — you will now need an external plugin like rollup-plugin-css-only to extract your styles to .css files as demonstrated in the template (#​147)
• Breaking: Options to be passed directly to the Svelte compiler must now go under a compilerOptions key in the plugin configuration object (#​145)
• Extend CompileOptions interface directly (#​126)
• Pass relative filename to svelte compiler (#​131)
• Link sourcemap with source correctly (#​140)
• Respect sourcemapExcludeSources Rollup config (#​93)
• Keep all sourcemaps from chunk (#​44)

---

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

[renovate]

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[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/eslint
npm ERR!   dev eslint@"5.16.0" from the root project
npm ERR!   peer eslint@"^5.0.0 || ^6.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"2.34.0" from the root project
npm ERR!   9 more (@typescript-eslint/experimental-utils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">=7.0.0" from [email protected]
npm ERR! node_modules/eslint-config-prettier
npm ERR!   dev eslint-config-prettier@"7.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=7.0.0" from [email protected]
npm ERR!   node_modules/eslint-config-prettier
npm ERR!     dev eslint-config-prettier@"7.2.0" 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! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-16T09_37_38_504Z-debug-0.log