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.

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

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

merged 1 commit into from Jul 11, 2022


Copy link

@renovate renovate bot commented Jul 11, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/parser (source) ^7.18.6 -> ^7.18.8 age adoption passing confidence
@babel/plugin-transform-typescript (source) ^7.18.6 -> ^7.18.8 age adoption passing confidence
@babel/standalone (source) ^7.18.7 -> ^7.18.8 age adoption passing confidence
@babel/types (source) ^7.18.7 -> ^7.18.8 age adoption passing confidence
@microsoft/api-extractor (source) ^7.28.2 -> ^7.28.4 age adoption passing confidence
@types/react ^18.0.14 -> ^18.0.15 age adoption passing confidence
@types/react-dom ^18.0.5 -> ^18.0.6 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.30.4 -> ^5.30.5 age adoption passing confidence
@typescript-eslint/parser ^5.30.4 -> ^5.30.5 age adoption passing confidence
core-js ^3.23.1 -> ^3.23.4 age adoption passing confidence
playwright-chromium (source) ^1.23.1 -> ^1.23.2 age adoption passing confidence
preact ^10.8.2 -> ^10.9.0 age adoption passing confidence
svelte (source) ^3.48.0 -> ^3.49.0 age adoption passing confidence
tailwindcss (source) ^3.1.4 -> ^3.1.5 age adoption passing confidence
ufo ^0.8.4 -> ^0.8.5 age adoption passing confidence
vite ^2.9.13 -> ^2.9.14 age adoption passing confidence
vitest ^0.17.0 -> ^0.18.0 age adoption passing confidence
vue-router ^4.0.16 -> ^4.1.1 age adoption passing confidence
vue-tsc ^0.38.2 -> ^0.38.4 age adoption passing confidence

Release Notes

babel/babel (@​babel/parser)


Compare Source

v7.18.8 (2022-07-08)

Thanks @​dbacarel for your first PR!

👓 Spec Compliance
🐛 Bug Fix
  • babel-plugin-transform-parameters
  • babel-plugin-transform-classes
  • babel-plugin-transform-for-of, babel-plugin-transform-spread, babel-traverse, babel-types
  • babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
📝 Documentation
🏠 Internal
🔬 Output optimization
Committers: 7
babel/babel (@​babel/plugin-transform-typescript)


Compare Source

👓 Spec Compliance
🐛 Bug Fix
  • babel-plugin-transform-parameters
  • babel-plugin-transform-classes
  • babel-plugin-transform-for-of, babel-plugin-transform-spread, babel-traverse, babel-types
  • babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
📝 Documentation
🏠 Internal
🔬 Output optimization
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)


Compare Source

Bug Fixes
  • eslint-plugin: [consistent-indexed-object-style] fix record mode fixer for generics with a default value (#​5280) (57f032c)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)


Compare Source

Note: Version bump only for package @​typescript-eslint/parser



Compare Source

  • Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of core-js
  • Added a fix of the FF103+ structuredClone bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but .stack of the clone is an empty string
  • Fixed { Map, WeakMap }.prototype.emplace logic, #​1102
  • Fixed order of errors throwing on iterator helpers


Compare Source


This patch includes the following bug fixes: - [BUG] LaunchOptions config has no effect after update to v1.23.0 - [REGRESSION]: Component testing project does not compile anymor - [BUG] Regression: page.on('console') is ignored in 1.23

Browser Versions
  • Chromium 104.0.5112.20
  • Mozilla Firefox 100.0.2
  • WebKit 15.4

This version was also tested against the following stable channels:

  • Google Chrome 103
  • Microsoft Edge 103


Compare Source

  • Improve performance of string escaping during SSR (#​5701)
  • Add ComponentType and ComponentProps convenience types (#​6770)
  • Add support for CSS @layer (#​7504)
  • Export CompileOptions from svelte/compiler (#​7658)
  • Fix DOM-less components not being properly destroyed (#​7488)
  • Fix class: directive updates with <svelte:element> (#​7521, #​7571)
  • Harden attribute escaping during SSR (#​7530)


Compare Source

  • Support configuring a default font-weight for each font size utility (#​8763)
  • Add support for alpha values in safe list (#​8774)
  • Improve types to support fallback values in the CSS-in-JS syntax used in plugin APIs (#​8762)
  • Support including tailwindcss and autoprefixer in postcss.config.js in standalone CLI (#​8769)
  • Fix using special-characters as prefixes (#​8772)
  • Don’t prefix classes used within arbitrary variants (#​8773)
  • Add more explicit types for the default theme (#​8780)


Compare Source



Compare Source

Please refer to for details.



Compare Source

   🚨 Breaking Changes
   🐞 Bug Fixes
    View changes on GitHub


Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub


Compare Source

Please refer to for details.


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 for details.



Compare Source

  • feat: add vueCompilerOptions.strictTemplates (#​1418)
  • fix: don't auto close ``` (#​1428)
  • fix: change unknown slot type from unknown to any (#​1541)
  • fix: SFC templates outline incorrect (#​1531)
  • fix: slot shorthand highlighting incorrect if have not = (#​1423)
  • fix: vue file import path auto-complete not working on windows (#​1304)
  • fix: avoid duplicate result in html (#​1552) (#​1530)
  • fix: code action document edit version incorrect (#​1490)

Breaking changes

  • experimentalSuppressUnknownJsxPropertyErrors, experimentalSuppressInvalidJsxElementTypeErrors is replaced by strictTemplates.

    	"vueCompilerOptions": {
    -		"experimentalSuppressUnknownJsxPropertyErrors": false,
    -		"experimentalSuppressInvalidJsxElementTypeErrors": false,
    +		"strictTemplates": true
Our Sponsors


Compare Source

  • feat: support html, css intellisense for petite-vue (#​1471)
  • fix: avoid unknown jsx property error for vue 2.7 (#​1533)
  • fix: fixed GlobalComponents interface not working edge case (#​1489)
  • fix: stricter slots type extracting (#​1522)
  • fix: nuxt app preview not working


📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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.

👻 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 11, 2022
Copy link

netlify bot commented Jul 11, 2022

Deploy Preview for vite-docs-main ready!

Name Link
🔨 Latest commit 47a62f3
🔍 Latest deploy log
😎 Deploy Preview
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

bluwy previously approved these changes Jul 11, 2022
@patak-dev patak-dev merged commit 6342140 into main Jul 11, 2022
@patak-dev patak-dev deleted the renovate/all-minor-patch branch July 11, 2022 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
dependencies Pull requests that update a dependency file
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants