fix(deps): update dependency vitepress to v0.22.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vitepress (source)	0.21.6 -> 0.22.4

---

Release Notes

vuejs/vitepress

v0.22.4

Compare Source

Bug Fixes

• plugin: set content-type header for serving index.html (#​616) (1656f03)
• remove 404 from title on initial route (#​590) (216e129), closes #​589

v0.22.3

Compare Source

Bug Fixes

• append base to links (#​502) (804954c), closes #​252
• avoid minimizing non-javascript inline scripts (#​517) (779b789), closes #​538 #​540
• client router: tolerant invalid hash selector typo (#​506) (ffe0c40)
• don't add .html to urls of non-html files (#​515) (34d1542), closes #​265
• normalize relative img src (#​514) (9270477), closes #​450
• require at least node v14 (#​546) (7cf7011)
• reset page data on 404 (#​497) (28eaa3b)

v0.22.2

Compare Source

Features

• improve default chunk strategy + page hash stability (1ef69e2)

v0.22.1

Compare Source

Features

• automatically update hash map + retry on failed page fetch (2324948)

• use git-based lastUpdated data (d32d8d4)

  Note: lastUpdated data is now disabled by default due to the performance overhead of retrieving the git information. This also means each page's metadata object no longer contains the lastUpdated property by default - it will only be present if the new lastUpdated: true config option is enabled.

v0.22.0

Compare Source

• Upgrade to Vite 2.8

0.21.6 (2022-01-19)

Perf

• Avoid wrapping siteData as readonly proxy in production builds

0.21.5 (2022-01-16)

Bug Fixes

• allow overriding title if home is true (#​493) (88d57a9)
• types: fix vitepress/theme type (eabf6d2), closes #​489 #​438 #​494 #​442

Features

• scrollOffset option (b66785d)

0.21.4 (2022-01-07)

Bug Fixes

• set __data in md.render (dfbc932)

0.21.3 (2022-01-06)

Bug Fixes

• prioritize vue installed in user project root (9b3243b)

0.21.2 (2022-01-06)

0.21.1 (2022-01-06)

Performance Improvements

• do not include head config in client bundle for production (6f3a96f)

---

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 has been generated by Mend 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: packages/el-table-next-docs/yarn.lock

npm WARN ignoring workspace config at /mnt/renovate/gh/jackluson/el-table-next/packages/el-table-next-docs/.npmrc 
npm ERR! Workspaces not supported for global packages

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-04-25T02_22_36_641Z-debug-0.log

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/jackluson/el-table-next/2pznit4DSZ9F9pad7CmLVsRLBpDY
✅ Preview: https://el-table-next-git-renovate-vitepress-0x-jackluson.vercel.app

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
el-table-next	✅ Ready (Inspect)	Visit Preview	May 6, 2022 at 11:33AM (UTC)

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.