Closed greenkeeper[bot] closed 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 π¨
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)The new version differs by 19 commits .
c0ad75b
[release] 2.2.5
b876395
[build] 2.2.5
bfeb28f
pin todomvc css version
3b7cfc7
coverage
f4630d0
treat with different types as different nodes (fix #5266)
5222f06
bump deps
6de1b9b
optimize patch conditionals
0bb529a
also warn when listening to camelCase events in in-DOM templates
e47b1e5
Allow named properties on reactive arrays. (#5216)
70db229
handle v-model on password input field on ie9 (fix #5250) (#5253)
23a058e
fix(inject): change warn message when trying to mutate an injected value (#5243)
7dea9f1
fix provide isn't reactive with a single array (#5229)
4c4a2ab
trigger event after reassigned state - Fix #5191 (#5233)
e733e5c
fix SSR v-show render. (#5224)
84856a3
update issue template
There are 19 commits in total. See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
vue-router
(vuejs/vue-router#1279)The new version differs by 6 commits .
0cebdf5
[release] 2.2.6
113fce9
[build] 2.2.6
6fcfdbd
warn and handle missing get in computed (fix #5265) (#5267)
3209f6f
remove parent/ref elm references when destroying instance, fix memory leak (fix vue-router#1279)
be07617
fix a typo (#5284)
8a518c1
update sponsors and backers
See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
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 decodedThe new version differs by 132 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 132 commits in total.
See the full diff
Your tests are passing again with this version. Explicitly upgrade to this version π
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.The new version differs by 143 commits0.
6b4f3da
[release] 2.3.1
2355318
[build] 2.3.1
ebd0338
introduce previous behavior as runInNewContext:"once"
cab1b15
avoid swallowing webpack error when entry is not found (fix #5553)
2a1f79d
run bundle in the same global context when runInNewContext is false (fix #5559)
9478fde
tweak type definition layouting (#5564)
228f0f8
remove unnecessary :any castings due to improved flow checks
3b426ef
Fix when functional component render method retrun null (fix #5536) (#5539)
bb7c543
fix #5539: improve isDef
type definition (#5549)
1635ca7
[vue-server-renderer] ensure assets are unique (#5540)
d6c070d
link to latest info
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
There are 143 commits in total.
See the full diff
Your tests are passing again with this version. Explicitly upgrade to this version π
this.$ssrContext
*.vue
components style SSR injectionsThe new version differs by 147 commits0.
b977c77
[release] 2.3.2
60291f2
[build] 2.3.2
8dc4215
improvements for handling vue-loader functional components with style injections
8d7ad19
expose $ssrContext
6b4f3da
[release] 2.3.1
2355318
[build] 2.3.1
ebd0338
introduce previous behavior as runInNewContext:"once"
cab1b15
avoid swallowing webpack error when entry is not found (fix #5553)
2a1f79d
run bundle in the same global context when runInNewContext is false (fix #5559)
9478fde
tweak type definition layouting (#5564)
228f0f8
remove unnecessary :any castings due to improved flow checks
3b426ef
Fix when functional component render method retrun null (fix #5536) (#5539)
bb7c543
fix #5539: improve isDef
type definition (#5549)
1635ca7
[vue-server-renderer] ensure assets are unique (#5540)
d6c070d
link to latest info
There are 147 commits in total.
See the full diff
Your tests are passing again with this version. Explicitly upgrade to this version π
Vue.use
not chainable when plugin has already been installed, also makes Vue.mixin
chainable. (@lzxb via #5610)v-for
v-for
being unnecessarily recreated (@gebilaoxiong via #5627)The new version differs by 166 commits0.
8d56a49
[release] 2.3.3
6bdaeb0
[build] 2.3.3
aaad733
improve scoped slot test case (#5640)
e70f191
no need to test composition events on Android
38759a6
fix test case in IE
8d54aec
async components: timeout should not trigger if already resolved (fix #5635)
3139605
ignore ssr getter
0ccefff
support v-for on scoped slots (fix #5615)
dc00590
comments
ec70b44
tweak noramlizeArrayChildren
f2bd882
Fix: nested child elements can not be updated correctly, fix #5618 (#5627)
5d965d5
clone isComment
when cloneVNode (#5633)
b5b1ac3
improve mutli-line &&
coding style to keep consistence (#5625)
1c40e32
Fix use mixin API feat continuous operation (#5610)
ca02043
avoid using native as identifier (close #5623)
There are 166 commits in total.
See the full diff
Your tests are still failing with this version. Compare the changes π¨
data.pendingInsert
The new version differs by 169 commits.
1f9416d
[release] 2.3.4
97b07be
[build] 2.3.4
33a25e7
prevent data.pendingInsert to keep reference to removed nodes (fix #5839)
8d56a49
[release] 2.3.3
6bdaeb0
[build] 2.3.3
aaad733
improve scoped slot test case (#5640)
e70f191
no need to test composition events on Android
38759a6
fix test case in IE
8d54aec
async components: timeout should not trigger if already resolved (fix #5635)
3139605
ignore ssr getter
0ccefff
support v-for on scoped slots (fix #5615)
dc00590
comments
ec70b44
tweak noramlizeArrayChildren
f2bd882
Fix: nested child elements can not be updated correctly, fix #5618 (#5627)
5d965d5
clone isComment
when cloneVNode (#5633)
There are 169 commits in total.
See the full diff
Version 2.2.3 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 :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/kopterio/vue-auth-cognito/builds/210474749)Release Notes
v2.2.3Notable Changes
Vue.config.performance
now defaults tofalse
due to its impact on dev mode performance. Only turn it on when you need it.Improvements
Fixed
.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.Commits
The new version differs by 16 commits .
d185dd2
[release] 2.2.3
b28aa39
[build] 2.2.3
368a335
perf code coverage
0416839
improve camelCase prop warning message
c6ab2e0
warn when template contains text outside root element (#5164)
025e763
Warn when not passing props in kebab-case (#5161)
4d227b9
turn off perf timeline measuring by default + reduce its impact on dev time perf (fix #5174)
a6e1ae0
v-bind object should have lower priority than explicit bindings (fix #5150)
e7dfcc3
fix custom directive arg fall through (fix #5162)
0b964c8
formatting tweaks
045ff5d
refactor create-component
4964b25
fix wrong order of generate modifier code (#5147)
f9706dc
fix v-on unit test (#5144)
8fca83d
fix #5121: parse content in textarea as plaintext (#5143)
82bc8b7
Merge branch 'dev' of github.com:vuejs/vue into dev
There are 16 commits in total. See the full diff.
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: