Update jest-vue-preprocessor to the latest version 🚀 #300
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.
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.0.0 of jest-vue-preprocessor was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of jest-vue-preprocessor.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.0.02.0.0 (2018-03-13)
BREAKING CHANGES
none, but in the future $el should be
defined, as it can't be used for testing if it's
undefined
fix(test): behaves differently locally
test behaves differently on travis-ci than
on my local machine, so now there is a test
to document that
none
fix(test): typeof didn't work
tried to use typeof, decided to use
casting
no breaking changes
context is needed for mounting functional components
but not as an option for a render function
no breaking changes
was passing an expression not a function
to onClick handler
no breaking changes
'@click="() => props.onClick('stuff')"
No breaking changes
can't reproduce $el.querySelector being defined
locally, yet on travis-ci it's defined.
Without it being defined I can't debugger and
figure out what the mock function isn't being called.
except for testing that mockFn was called
Commits
The new version differs by 5 commits.
df9d528
ci(travis): Remove yarn installation on travis (#54)
75d5f37
chore(node): Update node engines in package.json to 8.9 (#53)
c0c0590
Support for Functional Components (#50)
1df50d7
Show message from Babel (#45)
8fec8a2
Update prettier settings (#40)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴