chore(deps): update all non-major dependencies #9022
Merged
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:
^7.18.6
->^7.18.8
^7.18.6
->^7.18.8
^7.18.7
->^7.18.8
^7.18.7
->^7.18.8
^7.28.2
->^7.28.4
^18.0.14
->^18.0.15
^18.0.5
->^18.0.6
^5.30.4
->^5.30.5
^5.30.4
->^5.30.5
^3.23.1
->^3.23.4
^1.23.1
->^1.23.2
^10.8.2
->^10.9.0
^3.48.0
->^3.49.0
^3.1.4
->^3.1.5
^0.8.4
->^0.8.5
^2.9.13
->^2.9.14
^0.17.0
->^0.18.0
^4.0.16
->^4.1.1
^0.38.2
->^0.38.4
Release Notes
babel/babel (@babel/parser)
v7.18.8
Compare Source
v7.18.8 (2022-07-08)
Thanks @dbacarel for your first PR!
👓 Spec Compliance
babel-parser
,babel-types
@babel/types
AST definitions (@JLHwung)🐛 Bug Fix
babel-plugin-transform-parameters
babel-plugin-transform-classes
super(...)
calls (@dbacarel)babel-plugin-transform-for-of
,babel-plugin-transform-spread
,babel-traverse
,babel-types
babel-helper-module-transforms
,babel-plugin-transform-modules-commonjs
cjs
exports when transforming mutations (@nicolo-ribaudo)📝 Documentation
🏠 Internal
babel-types
babel-helper-fixtures
,babel-parser
🔬 Output optimization
babel-plugin-transform-typescript
Committers: 7
babel/babel (@babel/plugin-transform-typescript)
v7.18.8
Compare Source
👓 Spec Compliance
babel-parser
,babel-types
@babel/types
AST definitions (@JLHwung)🐛 Bug Fix
babel-plugin-transform-parameters
babel-plugin-transform-classes
super(...)
calls (@dbacarel)babel-plugin-transform-for-of
,babel-plugin-transform-spread
,babel-traverse
,babel-types
babel-helper-module-transforms
,babel-plugin-transform-modules-commonjs
cjs
exports when transforming mutations (@nicolo-ribaudo)📝 Documentation
🏠 Internal
babel-types
babel-helper-fixtures
,babel-parser
🔬 Output optimization
babel-plugin-transform-typescript
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.30.5
Compare Source
Bug Fixes
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.30.5
Compare Source
Note: Version bump only for package @typescript-eslint/parser
zloirock/core-js
v3.23.4
Compare Source
core-js
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{ Map, WeakMap }.prototype.emplace
logic, #1102Microsoft/playwright
v1.23.2
Compare Source
Highlights
This patch includes the following bug fixes:
https://github.com/microsoft/playwright/issues/15273 - [BUG] LaunchOptions config has no effect after update to v1.23.0https://github.com/microsoft/playwright/issues/153511 - [REGRESSION]: Component testing project does not compile anymorhttps://github.com/microsoft/playwright/issues/1543131 - [BUG] Regression: page.on('console') is ignored in 1.23
Browser Versions
This version was also tested against the following stable channels:
sveltejs/svelte
v3.49.0
Compare Source
ComponentType
andComponentProps
convenience types (#6770)@layer
(#7504)CompileOptions
fromsvelte/compiler
(#7658)class:
directive updates with<svelte:element>
(#7521, #7571)tailwindlabs/tailwindcss
v3.1.5
Compare Source
Added
font-weight
for each font size utility (#8763)Fixed
tailwindcss
andautoprefixer
inpostcss.config.js
in standalone CLI (#8769)unjs/ufo
v0.8.5
Compare Source
vitejs/vite
v2.9.14
Compare Source
Please refer to CHANGELOG.md for details.
vitest-dev/vitest
v0.18.0
Compare Source
🚨 Breaking Changes
ctx.log
toctx.logger.log
, improve log flicking - by @userquin and @antfu in https://github.com/vitest-dev/vitest/issues/1166🐞 Bug Fixes
ctx.cache
- by @antfu (695a7)View changes on GitHub
v0.17.1
Compare Source
🚀 Features
forceRerunTriggers
- by @elliotwestlake and @sheremet-va in https://github.com/vitest-dev/vitest/issues/1595🐞 Bug Fixes
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 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.
johnsoncodehk/volar
v0.38.4
Compare Source
vueCompilerOptions.strictTemplates
(#1418)unknown
toany
(#1541)=
(#1423)Breaking changes
experimentalSuppressUnknownJsxPropertyErrors
,experimentalSuppressInvalidJsxElementTypeErrors
is replaced bystrictTemplates
.Our Sponsors
v0.38.3
Compare Source
GlobalComponents
interface not working edge case (#1489)Configuration
📅 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.
This PR has been generated by Mend Renovate. View repository job log here.