chore(deps): update vue monorepo - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vue/cli-plugin-babel	4.5.13 -> 4.5.17
@vue/cli-plugin-e2e-cypress	5.0.0 -> 5.0.4
@vue/cli-plugin-eslint	4.5.13 -> 4.5.17
@vue/cli-plugin-unit-jest	4.5.13 -> 4.5.17
@vue/cli-service (source)	4.5.13 -> 4.5.17

---

Release Notes

vuejs/vue-cli

v4.5.17

Compare Source

🐛 Bug Fix

• @vue/cli-shared-utils, @vue/cli-ui
  • d7a9881 fix: replace node-ipc with @achrinza/node-ipc to further secure the dependency chain

Committers: 1

• Haoqun Jiang (@​sodatea)

v4.5.16

Compare Source

🐛 Bug Fix

• @vue/cli-service
  • Fix demo-lib.html and demo-wc.html for Vue 2
• @vue/cli-shared-utils, @vue/cli-ui
  • Lock node-ipc to v9.2.1

v4.5.15

Compare Source

Bug Fixes

• fix: set .mjs file type to javascript/auto [15b1e1b]

This change allows an .mjs file to import named exports from .cjs and plain .js files.
Fixes compatibility with pinia.

v4.5.14

Compare Source

Security Fixes

This version fixed a CORS vulnerability and an XSS vulnerability in Vue CLI UI.
We recommend all users of vue ui to upgrade to this version as soon as possible.

Credits:

Ngo Wei Lin (@​Creastery) of STAR Labs (@​starlabs_sg)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[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: frontend/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: frontend@0.1.0
npm ERR! Found: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"7.32.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">= 1.6.0 < 7.0.0" from @vue/cli-plugin-eslint@4.5.17
npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR!   dev @vue/cli-plugin-eslint@"4.5.17" 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/2022-04-10T18_51_50_357Z-debug-0.log