chore(deps): update dependency unplugin-vue-router to ^0.8.5 (main) #25913
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.7.0
->^0.8.3
Release Notes
posva/unplugin-vue-router (unplugin-vue-router)
v0.8.3
Compare Source
Bug Fixes
v0.8.2
Compare Source
Bug Fixes
v0.8.1
Compare Source
Bug Fixes
v0.8.0
Compare Source
Based on the feedback of the RFC, the Data Loaders have been redesigned from the ground up and are now way more flexible and powerful. As a result, if you were using the experimental data loaders, make sure to check the list of breaking changes and the new RFC at https://uvr.esm.is/rfcs/data-loaders. We are looking for early testers and feedback!
For people using the file-based routing, you now need to add
unplugin-vue-router/client
to thetypes
property of your tsconfig. See setup for an example.Bug Fixes
vue-router/auto-routes
(2dc0446)Code Refactoring
pending
toisLoading
(9502751)setupLoaderGuard
(8094f62)Features
Performance Improvements
BREAKING CHANGES
Remove the deprecated APIs:
createPrefixTree()
->new PrefixTree()
VueRouterExports
->VueRouterAutoImports
Data Loaders have been redesigned to be more flexible
and account for other libraries. Notably, the caching behavior has been
moved out of the basic loader to an extended one pinia-colada and the basic loader
has no cache. All of the pending bugs have also been fixed.
I recommend you to give the RFC examples a new read to get
setup: https://uvr.esm.is/rfcs/data-loaders/. Most of the changes are
simplifying things by removing them.
Here is a list of the breaking changes to simplify
migration:
dataFetching
option is no longer needed.HasDataLoaderMeta
has beenremoved. It is just no longer needed. Loaders are picked up from lazy
loaded components and must otherwise be directly added to a
meta.loaders
array. See the example at https://uvr.esm.is/rfcs/data-loaders/#basic-example
setupDataFetchingGuard
has been replaced with a VuePlugin. See https://uvr.esm.is/rfcs/data-loaders/#data-loader-setup
for details.
cacheTime
, use thestaleTime
option in thenew
defineColadaLoader()
based off @pinia/coladarefactored and none of the defineLoader functions are automatically
imported anymore. You can add them yourself to the list of auto
imports, or import them from
vue-router/auto
. The good news is youno longer need to use the plugin in order to benefit from the data
loaders; they can be directly imported from
unplugin-vue-router/runtime
even if you don't want file-based routing.If you find missing information or improvements, please open a Pull
Request to improve the
CHANGELOG.md
.plugin:
Replace
with
vue-router/auto/routes
becomesvue-router/auto-routes
. This change was necessary to improve compatibility withTypeScript and other tools in the ecosystem. Most of the time you don't
need to use this path but if you were using it, replace it:
Data Loaders now return an
isLoading
property insteadof
pending
. This aligns better with the wording of Data Loaders beingin a loading state rather than pending, which can have more meanings.
You know need to add
unplugin-vue-router/client
to thetypes
property of your tsconfig. See setup for an example.the existing
defineLoader
is being replaced by abasic loader without cache. The version with cache will be implemented
by adding a library that properly handles the caching. This new strategy
will also enable other integrations like VueFire, Apollo, and custom
ones. Keep an eye (subscribe) to the RFC for news and to discus abhttps://github.com/vuejs/rfcs/discussions/460://github.com/Vue Router Data Loaders vuejs/rfcs#460
since data loaders aren't meant to be awaited in script
setup (they are awaited at the navigation level), they now return a
promise of the raw data only, not of the UseDataLoaderReturn, to make it
clearer that this syntax is a bit special and should only be used within
nested loaders. This change also brings other benefits like allowing
lazy loaders to be awaited within loaders without changing their usage
outside, in components. Also, allowing different types of commit while
still allowing data to be awaited within loaders.
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 has been generated by Mend Renovate. View repository job log here.