You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2023. It is now read-only.
This version is covered by your current version range and after updating it in your project the build failed.
As vue is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/posva/vue-mdc/910?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Release Notesv2.3.0 JoJo's Bizarre Adventure
🚀 New
Server-Side Rendering Improvements
Note: We have created a brand-new standalone guide for server-side rendering in Vue, it's a recommended read for all users. Also, the HackerNews demo has been updated to reflect the latest best practices.
Now uses the data-server-rendered attribute to indicate server-rendered markup, making the output valid HTML.
template option now supports simple interpolation using the render context. This allows the template to be dynamic based on the data attached to the context by rendered components.
Defaults to true, which preserves the original behavior.
When set to false, the renderer will no longer re-execute the entire bundle in a new vm context for each render. Instead, only the function exported by the bundle will be called again. This greatly improves performance, but requires some changes in source code structure.
By passing the bundleRender a client webpack build manifest generated by vue-server-renderer/client-plugin, the renderer can infer the proper build assets that need to be preloaded (e.g. code-split async chunks, images, and fonts). When using together with the template option, <link rel="preload/prefetch"> and appropriate <script> tags will be injected automatically.
vue-ssr-webpack-plugin is now deprecated, instead, it is now part of vue-server-renderer. It now also exposes two plugins - one for the server build and one for the client build.
var VueSSRServerPlugin =require('vue-server-renderer/server-plugin')
var VueSSRClientPlugin =require('vue-server-renderer/client-plugin')
Async component factories can now return an object of the following format:
constAsyncComp= () => ({
// The component to load. Should be a Promise
component:import('./MyComp.vue'),
// A component to use while the async component is loading
loading: LoadingComp,
// A component to use if the load fails
error: ErrorComp,
// Delay before showing the loading component. Defaults to 200ms.
delay:200,
// The error component will be displayed if a timeout is provided and exceeded.
timeout:3000
})
Note that when used as a route component in vue-router, these properties will be ignored because async components are resolved upfront before the route navigation happens. You also need to update vue-router to 2.4.0+ if you wish to use the new syntax for route components.
Functional Component Improvements
Functional components can now omit the props option. All attributes will be automatically extracted and exposed as camelized props on context.props.
Note when the props option is provided, it will retain the old behavior - i.e. only explicitly declared props will be extracted.
v-on listeners attached to a functional component will be exposed as context.listeners. This is simply an alias to context.data.on.
Combined with the props change, functional components usage can be much cleaner:
Functional components now also support the inject option. Injected properties are exposed as context.injections. (@Kingwl via #5204)
Other Improvements
.sync is back! However it now is simply syntax sugar that expands into a prop + listener pair, similar to v-model.
The following
<comp :foo.sync="bar"></comp>
is expanded into:
<comp :foo="bar" @update:foo="val => bar = val"></comp>
For the child component to update foo's value, it needs to explicitly emit an event instead of mutating the prop:
this.$emit('update:foo', newValue)
Warnings now include component hierarchy traces.
Vue.config.errorHandler now also handles error thrown inside custom directive hooks (@xijiongbo via #5324)
Vue.config.errorHandler now also handles error thrown in nextTick callbacks.
New v-on modifier: .passive - adds the event listener with { passive: true }. (@Kingwl via #5132)
Props validation now supports type: Symbol.
style bindings now support using an Array to provide multiple (prefixed) values to a property, so the following would be possible (@fnlctrl via #5460):
Version 2.3.0 of vue just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As vue is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/posva/vue-mdc/910?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)Release Notes
v2.3.0 JoJo's Bizarre Adventure🚀 New
Server-Side Rendering Improvements
Note: We have created a brand-new standalone guide for server-side rendering in Vue, it's a recommended read for all users. Also, the HackerNews demo has been updated to reflect the latest best practices.
Now uses the
data-server-rendered
attribute to indicate server-rendered markup, making the output valid HTML.template
option now supports simple interpolation using the render context. This allows the template to be dynamic based on the data attached to the context by rendered components.See docs for more details.
New
bundleRenderer
option:runInNewContext
Defaults to
true
, which preserves the original behavior.When set to
false
, the renderer will no longer re-execute the entire bundle in a new vm context for each render. Instead, only the function exported by the bundle will be called again. This greatly improves performance, but requires some changes in source code structure.See docs for more details.
New
bundleRenderer
option:clientManifest
By passing the
bundleRender
a client webpack build manifest generated byvue-server-renderer/client-plugin
, the renderer can infer the proper build assets that need to be preloaded (e.g. code-split async chunks, images, and fonts). When using together with thetemplate
option,<link rel="preload/prefetch">
and appropriate<script>
tags will be injected automatically.See docs for more details.
vue-ssr-webpack-plugin
is now deprecated, instead, it is now part ofvue-server-renderer
. It now also exposes two plugins - one for the server build and one for the client build.See docs for more details.
Async Component Improvements
Async component factories can now return an object of the following format:
Note that when used as a route component in
vue-router
, these properties will be ignored because async components are resolved upfront before the route navigation happens. You also need to updatevue-router
to 2.4.0+ if you wish to use the new syntax for route components.Functional Component Improvements
Functional components can now omit the
props
option. All attributes will be automatically extracted and exposed as camelized props oncontext.props
.Note when the
props
option is provided, it will retain the old behavior - i.e. only explicitly declared props will be extracted.v-on
listeners attached to a functional component will be exposed ascontext.listeners
. This is simply an alias tocontext.data.on
.Combined with the
props
change, functional components usage can be much cleaner:Functional components now also support the
inject
option. Injected properties are exposed ascontext.injections
. (@Kingwl via #5204)Other Improvements
.sync
is back! However it now is simply syntax sugar that expands into a prop + listener pair, similar tov-model
.The following
is expanded into:
For the child component to update
foo
's value, it needs to explicitly emit an event instead of mutating the prop:Warnings now include component hierarchy traces.
Vue.config.errorHandler
now also handles error thrown inside custom directive hooks (@xijiongbo via #5324)Vue.config.errorHandler
now also handles error thrown innextTick
callbacks.New
v-on
modifier:.passive
- adds the event listener with{ passive: true }
. (@Kingwl via #5132)Props validation now supports
type: Symbol
.style
bindings now support using an Array to provide multiple (prefixed) values to a property, so the following would be possible (@fnlctrl via #5460):An extended component constructor can now also be used as a
mixin
. (@ktsn via #5448)🐛 Fixed
v-model
not syncing for autocomplete / switching focus before confirming compositionclass
and:class
together in Edgev-model
checkbox binding with Array index (@posva via #5402)0
(@posva via #5481)<script type="x/template">
being unnecessarily decodedCommits
The new version differs by 126 commits0.
a27c464
[release] 2.3.0
87b0d5d
[build] 2.3.0
d8315c4
do not decode text inside script/style tags (fix #5526)
3a6fd13
[release] 2.3.0-beta.1
56b6f8a
[build] 2.3.0-beta.1
cb0531c
increase async delay for more test cases
c24f492
fix edge test case
1096890
increase async component test delay
12b7122
fix mixin issue (#5514)
2a247fc
fix ssr initial context style recording
016920e
support customizing context and window keys for renderState()
38516b4
fix flow
380e988
Allow slot names to be numbers (#5481)
1288386
Support Vue.delete(arr, index) in TypeScript definitions (#5508)
a2f57e3
use context-agnostic RegExp check
There are 126 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: