Open greenkeeper[bot] opened 7 years ago
After pinning to 2.3.4 your tests are passing again. Downgrade this dependency 📌.
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
Your tests are passing again with this version. Explicitly upgrade to this version 🚀
<pre>
082fc39, closes #6146<select>
option update c70addf, closes #6112The new version differs by 21 commits.
b8f1bcd
build: release 2.4.2
fd68195
build: build 2.4.2
f104b84
build: tweak release note file default name
ec4b1be
revert: perf: remove src directory from npm module (#6072)
3d14e85
fix: checkbox v-model="array" ignore false-value (#6180)
3036551
fix(provide/inject): merge provide properly from mixins
fc3d7cd
fix: work around IE/Edge bug when accessing document.activeElement from iframe
eb9168c
feat: warn when assigning to computed property with no setter
a8ac129
fix: ensure looseEqual is not dependant on key enumeration order
9b4dbba
fix(transition): should trigger transition hooks for v-show in ie9
082fc39
fix(parser): only ignore the first newline in
1713061
fix(v-on): revert component root data.on/data.nativeOn behavior for
06b9b0b
fix(v-bind): respect .prop modifier on components (#6159)
d03fa26
fix(compile): properly generate comments with special character (#6156)
b0f00e3
fix(provide/inject): resolve inject properly from mixins (#6107)
There are 21 commits in total.
See the full diff
Version 2.4.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.
vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ✅ **pyup.io/safety-ci** No dependencies with known security vulnerabilities. [Details](https://pyup.io/repos/github/OGKevin/ComBunqWebApp/commits/1ae267c421280c93c66b7340caa362a112128279/) - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/OGKevin/ComBunqWebApp/builds/253079926?utm_source=github_status&utm_medium=notification)Release Notes
v2.4.0 Kill la KillFeatures
Full SSR + async component support in core: SSR now supports rendering async components used anywhere and the client also supports async components during the hydration phase. This means async components / code-splitting now just works during SSR and is no longer limited at the route level. (9cf6646 & 7404091)
Easier creation of wrapper components: (6118759)
New component option:
inheritAttrs
. Turns off the default behavior whereparent scope non-prop bindings are automatically inherited on component root
as attributes.
New instance properties:
$attrs
&$listeners
.$attrs
contains the parent-scope attribute bindings that were not recognized as props, and$listeners
contains thev-on
listeners registered in the parent scope (without the.native
modifier). These are essentially aliases of$vnode.data.attrs
and$vnode.data.on
, but are reactive.Combining these allows us to simplify a component like this down into this:
Based on discussion in #5983.
v-on: support
v-on
object syntax with no arguments. This pairs well with the new$listeners
instance property when creating higher-order components. Note this syntax does not support modifiers. (11614d6)Now auto-resolves ES module
default
export when resolving async components. This enables keeping using the simplerconst Foo = () => import('./Foo.vue')
syntax when declaring async components with the changes introduced in vue-loader@13.0.0. (0cd6ef3)support
.sync
modifier forv-bind="object"
(#5943) (3965e50), closes #5937keep-alive: support Array for include and exclude (#5956) (51c595a)
weex: implement "weex.supports" api to support feature detection (#6053) (b1512d8)
vm.$watch
now also supports using the same object format supported by thewatch
component option:{ handler: () => {}, deep: true }
(#5645) (5aac170)types: add types for
vue-server-renderer
(#5775) (e6de9a5)Vue.config.errorHandler
now also captures errors thrown in custom event handlers (#5709) (11b7d5d)add new config option
Vue.config.warnHandler
for defining a custom callback for runtime warnings. This only works in the development build. (#5883) (9881b40)add
comments
option to allow preserving comments in template (#5951) (e4da249), closes #5392Performance Improvements
ssr:
vue-template-compiler
now has two new SSR-specific compile methods that generates SSR-specific render function code by optimizing parts of the template into string concatenation. This improves raw SSR render performance by 2~8x depending on how much of the template can be optimized. Note this will have a much smaller impact on requests per second for a real app because raw render performance is only a small portion of the overall time spent in a request.This is enabled by default in
vue-loader@>=12
and can be disabled using the optimizeSSR option.remove src directory from npm module, which should reduce download size when installing from npm. (#6072) (e761573)
Bug Fixes
as
attribute (#5683) (ebca266)Vue.set
on Array (#5889) (8a2c514)is
,ref
, ...) inv-bind
object syntax (#5881) (d33c125)Commits
The new version differs by 143 commits ahead by 143, behind by 3.
ac3d1ea
build: release 2.4.0
1bdea82
build: build 2.4.0
529e3db
build: update build script
e0ca894
test: improve coverage
92a5e93
build: update release note script
086e6d9
fix: handle arrays in v-on object syntax
dc1bca1
chore: document new ssr methods in vue-template-compiler
67fe6cb
test: use latest mobile browsers on saucelabs
e761573
perf: remove src directory from npm module (#6072)
754e041
remove references to gitter; use chat.vuejs.org for discourse (#6084)
485e740
test: make tests pass in IE
91deb4f
fix: multiple merged vnode hooks not invoked properly
6bf9772
feat(ssr): inheritAttrs support in SSR
1bf98b0
test: adjust transition tests for firefox
606666d
test: fix Object.prototype.watch related warnings
There are 143 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: