-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency vue-router to v4.5.0 #64
base: deps
Are you sure you want to change the base?
Conversation
8b8655d
to
15f0448
Compare
15f0448
to
bc8d992
Compare
bc8d992
to
e3cb978
Compare
e3cb978
to
f506151
Compare
f506151
to
0c41046
Compare
0c41046
to
c5290c3
Compare
c5290c3
to
7b78394
Compare
7b78394
to
2d7541e
Compare
2d7541e
to
61c65e1
Compare
61c65e1
to
4f82010
Compare
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
4f82010
to
2a4eb99
Compare
2a4eb99
to
9487f5d
Compare
9487f5d
to
b0185c2
Compare
|
b0185c2
to
2b9d446
Compare
2b9d446
to
c2719c9
Compare
c2719c9
to
285d803
Compare
285d803
to
2fd6c01
Compare
2fd6c01
to
c1de7b6
Compare
c1de7b6
to
ac39b6b
Compare
ac39b6b
to
e94ac6b
Compare
This PR contains the following updates:
4.0.12
->4.5.0
Release Notes
vuejs/router (vue-router)
v4.5.0
Compare Source
Please refer to CHANGELOG.md for details.
v4.4.5
Compare Source
Please refer to CHANGELOG.md for details.
v4.4.4
Compare Source
Please refer to CHANGELOG.md for details.
v4.4.3
Compare Source
Please refer to CHANGELOG.md for details.
v4.4.2
Compare Source
Please refer to CHANGELOG.md for details.
v4.4.1
Compare Source
v4.4.0
Compare Source
Please refer to CHANGELOG.md for details.
v4.3.3
Compare Source
Please refer to CHANGELOG.md for details.
v4.3.2
Compare Source
Please refer to CHANGELOG.md for details.
v4.3.1
Compare Source
Please refer to CHANGELOG.md for details.
v4.3.0
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.5
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.4
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.3
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.2
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.1
Compare Source
Please refer to CHANGELOG.md for details.
v4.2.0
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.6
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.5
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.4
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.3
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.2
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.1
Compare Source
Please refer to CHANGELOG.md for details.
v4.1.0
Compare Source
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 routesIt'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 apath
and users often found themselves defining a pass through component that would just render a<RouterView>
component to reuse thepath
structure. You can now simplify this to: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 astate
property when callingrouter.push()
orrouter.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:To see a full example, check the modal e2e test, it has been updated to use the
state
property.It's worth noting this shouldn't be used to pass fetched data or complex objects such as classes because of type and size limitations. Check the History State documentation for more information about the
state
property.Given the nature of the
<RouterView>
'sroute
prop, there is also a new functionloadRouteLocation()
that can be used on a resolved route location to load a route with lazy loading:Typed Routes
In v4.1 we were initially planning to introduce types to automatically detect the params from a
path
property, creating autocomplete and type safety inrouter.push()
and<RouterLink>
'sto
prop. It was implemented but also turned out to be extremely slow after ~50 routes due to the nature of the types relying on nesting and complex unions. Instead, we are introducing a build plugin to generate the types of the routes for you based your file structure. This is similar to Nuxt and Vite Plugin Pages but with full type support (similar to nuxt-typed-router) while allowing you to keep using the exact same API, just with Autocompletion and typing hints 😄. The plugin currently supports Vite, Webpack (with some caveats), and rollup and it's currently experimental to gather feedback from the community and build a flexible solution. We hope to release a stable version in the following months.Check out the plugin GitHub repository for installation instructions and documentation.
Here are some other examples of how much this plugin can improves your developer experience:
CJS/MJS support for Node
We now expose a few extra entry points for Node but kept the old ones as well to prevent any disruption to the existing users. You can find more information about this in the corresponding pull request.
Please refer to CHANGELOG.md for details.
v4.0.16
Compare Source
Please refer to CHANGELOG.md for details.
v4.0.15
Compare Source
Please refer to CHANGELOG.md for details.
v4.0.14
Compare Source
Please refer to CHANGELOG.md for details.
v4.0.13
Compare Source
Please refer to CHANGELOG.md for details.
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.
This PR was generated by Mend Renovate. View the repository job log.