Open greenkeeper[bot] opened 7 years ago
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Vue.config.performance
now defaults to false
due to its impact on dev mode performance. Only turn it on when you need it..prevent
modifier regression when combined with other key modifiers (@Kingwl via #5147)v-bind
object should have lower priority than explicit bindingsperformance.measure
in dev mode.Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
updated
hook not triggering update (@Kingwl via #5233)Vue.set
crashing when used on Arrays with non-number key (@pkaminski via #5216)v-show
not setting inline display property in SSR (@defcc via #5224)inject
option not reactive (@Kingwl via #5229)input[type=password]
behavior in IE9 (@ktsn via #5253)Your tests are still failing with this version. Compare the changes π¨
vue-router
(vuejs/vue-router#1279)Your tests are still failing with this version. Compare the changes π¨
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 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.
See docs for more details.
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')
See docs for more details.
Async component factories can now return an object of the following format:
const AsyncComp = () => ({
// 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 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:
const MyComp = {
functional: true,
render (h, { props, listeners }) {
return h('div', {
on: {
click: listeners.click // proxy click listener
}
}, [
props.msg // auto extracted props
])
)
}
Functional components now also support the inject
option. Injected properties are exposed as context.injections
. (@Kingwl via #5204)
.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):
<div :style="{ display: ["-webkit-box", "-ms-flexbox", "flex"] }">
An extended component constructor can now also be used as a mixin
. (@ktsn via #5448)
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 decodedYour tests are still failing with this version. Compare the changes π¨
null
(@gebilaoxiong via #5539)vue-server-renderer/server-plugin
: ensure assets are unique (@pi0 via #5540)vue-server-renderer/server-plugin
: avoid swallowing webpack error when entry is not foundvue-server-renderer
: with runInNewContext: false
, the bundle is now indeed executed in the same context. The 2.3.0 behavior is still available behind a new option value runInNewContext: 'once'
. See docs for more details.Your tests are still failing with this version. Compare the changes π¨
this.$ssrContext
*.vue
components style SSR injectionsYour tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
data.pendingInsert
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
<pre>
082fc39, closes #6146<select>
option update c70addf, closes #6112Your tests are still failing with this version. Compare the changes π¨
inject
option in functional component options type (#6530) 1baa0a7Your tests are still failing with this version. Compare the changes π¨
errorCaptured
hook b3cd9bc [Details]further improve Vue type declarations for canonical usage (#6391) db138e2
This change requires upgrade actions for TypeScript users using 2.4 types. For more details, please read this blog post.
renderToString
now returns a Promise if no callback is passed f881dd1, closes #6160shouldPrefetch
option (same signature as shouldPreload
) 7bc899c, closes #5964vue-server-renderer/basic.js
c5d0fa0 [Details]v-model
type
binding on <input>
f3fe012v-on
.exact
event modifier (#5977) 9734e87, closes #5976 [Details]<keep-alive>
max
prop for <keep-alive>
for limiting max number of instances cached 2cba6d4config.ignoredElements
can now contain RegExp in addition to strings (#6769) 795b908data
function is now called with the vm instance as the first argument (#6760) 3a5432avue-template-compiler
now ships an environment-agnostic build which can be used directly in browsers in vue-template-compiler/browser.js
a5e5b31Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Notable update: Type compatibility with TS 2.6
<select v-model>
initial state e1657fd, closes #6986Your tests are still failing with this version. Compare the changes π¨
@click.right
and @click.middle
daed1e7, closes #7020Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
core: prop bindings with inline Object/Array literal values no longer cause the child component to always re-render:
<foo :bar="[1, 2, 3]"/>
The compiler now automatically wraps the literal value as an inline computed property to avoid creating new values on each render (unless data it depends on has changed).
types: extract VueConfiguration type for easy expansion (#7274) c0d516c, closes #7273
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
listeners
type on RenderContext (#7584) db1b18c, closes #7584Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
devDependency
vue-template-compiler was updated from 2.5.17
to 2.5.18
.Your tests are still failing with this version. Compare changes
devDependency
vue-template-compiler was updated from 2.5.18
to 2.5.19
.Your tests are still failing with this version. Compare changes
Version 2.2.1 of vue-template-compiler just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As vue-template-compiler 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 :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/INTECH-RGB/homie-dashboard/builds/205504519)Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: