Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major dependencies #257

Merged
merged 1 commit into from Jul 11, 2022
Merged

chore(deps): update all non-major dependencies #257

merged 1 commit into from Jul 11, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 11, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@microsoft/api-extractor (source) 7.28.2 -> 7.28.4 age adoption passing confidence
@vue/test-utils ^2.0.0 -> ^2.0.2 age adoption passing confidence
@vueuse/core ^8.7.5 -> ^8.9.1 age adoption passing confidence
rollup (source) ^2.75.7 -> ^2.76.0 age adoption passing confidence
vite ^2.9.13 -> ^2.9.14 age adoption passing confidence
vue-demi ^0.13.1 -> ^0.13.2 age adoption passing confidence
vue-router ^4.0.16 -> ^4.1.1 age adoption passing confidence

Release Notes

vuejs/test-utils

v2.0.2

Compare Source

What's Changed

Fixes
Docs
Chore/Other

New Contributors

Full Changelog: vuejs/test-utils@v2.0.1...v2.0.2

v2.0.1

Compare Source

Test Utils is quite stable now, so most of the changes here are minor fixes.

The next "big ticket" feature will be SSR support. You can track it here: https://github.com/vuejs/test-utils/pull/1572

Fixes

Chores/Dependencies

#### New Contributors * @​dcrall made their first contribution in https://github.com/vuejs/test-utils/pull/1535 * @​snoozbuster made their first contribution in https://github.com/vuejs/test-utils/pull/1549

Full Changelog: vuejs/test-utils@v2.0.0...v2.0.1

vueuse/vueuse

v8.9.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v8.9.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v8.8.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v8.8.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
rollup/rollup

v2.76.0

Compare Source

2022-07-08

Features
  • Allow setting a sourcmapBaseUrl for absolute paths in sourcemaps (#​4527)
Bug Fixes
  • Support absolute CLI plugin paths on Windows (#​4533)
Pull Requests
vitejs/vite

v2.9.14

Compare Source

Please refer to CHANGELOG.md for details.

antfu/vue-demi

v0.13.2

Compare Source

   🚀 Features
    View changes on GitHub
vuejs/router

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 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:

// go to /users/24 but show a modal instead
router.push({ name: 'UserDetail', params: { id: 24 } state: { backgroundView: ... } })

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>'s route prop, there is also a new function loadRouteLocation() that can be used on a resolved route location to load a route with lazy loading:

import { loadRouteLocation } from 'vue-router'

const loadedRoute = await loadRouteLocation(router.resolve('/users/24'))

Typed Routes

RouterLink to autocomplete

In v4.1 we were initially planning to introduce types to automatically detect the params from a path property, creating autocomplete and type safety in router.push() and <RouterLink>'s to 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:

params validation in RouterLink Route infer from if condition Typed routes in navigation guards

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.

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Jul 11, 2022

Codecov Report

Merging #257 (9887a68) into v1 (ed60743) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##              v1    #257   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          6       6           
  Lines        214     214           
  Branches      42      42           
=====================================
  Misses       202     202           
  Partials      12      12

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ed60743...9887a68. Read the comment docs.

@renovate renovate bot merged commit b01ca22 into v1 Jul 11, 2022
@renovate renovate bot deleted the renovate/all-minor-patch branch July 11, 2022 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants