Bump vue-router from 4.0.13 to 4.1.6

[dependabot]

Bumps vue-router from 4.0.13 to 4.1.6.

Release notes

Sourced from vue-router's releases.

v4.1.6

Please refer to CHANGELOG.md for details.

v4.1.5

Please refer to CHANGELOG.md for details.

v4.1.4

Please refer to CHANGELOG.md for details.

v4.1.3

Please refer to CHANGELOG.md for details.

v4.1.2

Please refer to CHANGELOG.md for details.

v4.1.1

Please refer to CHANGELOG.md for details.

v4.1.0

Vue Router 4.1

We are excited to announce the release of Vue Router 4.1 with a few new interesting features, better support for Node ESM and no breaking changes.

Omitting the component/components option in routes

It's now possible to completely omit the component option when defining routes with children. While nested routes are about defining layouts, they are also directly connected to a path and users often found themselves defining a pass through component that would just render a <RouterView> component to reuse the path structure. You can now simplify this to:

- import { RouterView } from 'vue-router'
- import { h } from 'vue'
-
 const routes = [
   {
     path: '/admin',
-     component: () => h(RouterView),
     children: [
       { path: 'users', component: AdminUserList },
       { path: 'users/:id', component: AdminUserDetails },
     ],
   },
 ]

In other words, you can now nest paths without having to define a component.

Passing History State in navigations

Passing History State through router.push() has been implemented and used by the router since its version 4.0 but hasn't been exposed as a public API until now. This enables passing a state property when calling router.push() or router.replace(). This is useful to pass global state to be associated with the history entry that cannot be shared by copying the URL. One common example of this are Modals:

</tr></table> 

... (truncated)

Commits

• 30002aa release: [email protected]
• b75f1ec chore: up chromedriver
• 756f755 feat(matcher): avoid empty records to be reached
• d218cca chore: up deps
• f02119f chore: update netlify
• 7841b74 docs: add .vue suffix
• dab08ae chore: fixed router/e2e/runner function name spell mistake (#1579)
• 3a939c9 Docs: Update Free Weekend Vue School banner (#1566)
• e40cd0b chore: bronze sponsor link [skip ci] (#1563)
• 658faea docs: add vuetoronto logo (#1559)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

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

Name	Status	Preview	Updated
sbp-partners	❌ Failed (Inspect)		Oct 25, 2022 at 3:05AM (UTC)