Open greenkeeper[bot] opened 7 years ago
Merging #90 into master will decrease coverage by
0.49%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #90 +/- ##
=========================================
- Coverage 12.8% 12.31% -0.5%
=========================================
Files 40 40
Lines 1015 1015
=========================================
- Hits 130 125 -5
- Misses 885 890 +5
Impacted Files | Coverage Ξ | |
---|---|---|
src/commands/index.js | 75.75% <0%> (-15.16%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update fe5bfde...37e27db. Read the comment docs.
Update to this version instead π
The new version differs by 8 commits ahead by 8, behind by 1.
a0fbd50
8.0.2
2004b91
require correct deps
fa56d21
Always use unpad (#535)
295091d
Allow ^ version for babel dependencies (#534)
d3b8519
fix(package): update babylon to version 7.0.0-beta.31 (#533)
54ab4ac
8.0.1
c1a7882
Update README.md support (#531) [skip ci]
51100c9
chore(package): update mocha to version 4.0.0 (#524)
See the full diff
Update to this version instead π
Use ESLint's API to customize scope analysis and avoid monkeypatching: #542
Update to this version instead π
The new version differs by 11 commits.
2bd8508
8.2.4
5881648
Add test for template string with object with template string inside (#639)
476426a
Support OptionalMemberExpression with scope too (#634)
92874d4
Drop node4 in travis
d2ac299
Bump Babel deps
e63962d
refactor: rename babylon to @babel/parser
873f02f
Fix converting template types to handle nested templates (#610)
74a3207
Fix token types for experimental operators (#632)
e802577
Add support for the optional chaining operator (#630)
ebc46e1
don't require unpad per test fixture, fixes #572 (#618)
9641e4b
updates readme for latest eslint & babel-eslint (#607) [skip ci]
See the full diff
Update to this version instead π
We've released v7: https://twitter.com/left_pad/status/1034204330352500736, so this just updates babel-eslint to use those versions internally. That in itself doesn't break anything but:
To enable the legacy decorators proposal users should add a specific parser option:
{
parserOptions: {
ecmaFeatures: {
legacyDecorators: true
}
}
}
The new version differs by 15 commits ahead by 15, behind by 2.
6aa8b6f
9.0.0
c7ee9ae
Bump to babel@7.0.0 π (#676)
3ece549
Docs: Make the default parserOptions more explicit (#673)
0b36951
Add logical assignment plugin (#674)
5856ff5
Bump some devDeps
45938d9
build(deps): upgrade @babel/* to 7.0.0-rc.2 (#668)
bc97875
9.0.0-beta.3
74c5d62
update lock
6a45632
chore - fixing eslint-scope to a safe version; resolves #656. (#657)
e0119e0
9.0.0-beta.2
198964b
Merge pull request #645 from rubennorte/support-new-flow-syntax-in-scope-analysis
9b06e1f
Added failing test for variables used in type parameters
8948d83
Upgrade Babel to v7.0.0-beta.52 (#650)
4882b29
9.0.0-beta.1
15e8d6f
Breaking: Upgraded Babel to 7.0.0-beta.51 (#642)
See the full diff
devDependency
babel-eslint was updated from 7.2.3
to 10.0.0
.Update to this version instead π
Small breaking change: add a peerDependency starting from the ESLint version that added a parser feature that we were monkeypatching before (and drop that code). If already using ESLint 5 shouldn't be any different.
TypeAlias
: #584/* @flow */
type Node<T> = { head: T; tail: Node<T> }
// or
type File = {chunks: Array<Chunk>}
type Chunk = {file: File}
devDependency
babel-eslint was updated from 7.2.3
to 10.0.1
.Update to this version instead π
The TypeAlias
"conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.
devDependency
babel-eslint was updated from 7.2.3
to 10.0.2
.Update to this version instead π
Fixes #772
devDependency
babel-eslint was updated from 7.2.3
to 10.0.3
.devDependency
babel-eslint was updated from 7.2.3
to 10.1.0
.
Version 8.0.0 of babel-eslint just got published.
The version 8.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of babel-eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v8.0.08.0.0
No major changes, just updating babel deps to v7
Commits
The new version differs by 22 commits.
905887c
8.0.0
49493e4
update to beta.0
42d0c5b
Remove already fixed workaround (#508)
25bd208
8.0.0-alpha.17
1468905
alpha.17
57c133e
8.0.0-alpha.15
1e41162
update (#504)
c31b577
Readme update usage section (#501) [skip ci]
c2626f9
Update eslint to the latest version π (#500)
3c6b2de
chore(package): update husky to version 0.14.0 (#498)
e052d5a
Update install instructions to use latest stable release (#497) [skip ci]
8e3e088
8.0.0-alpha.13
f757e22
Merge pull request #493 from danez/regression-test
5736be6
Update babylon
37f9242
Add Prettier (#491)
There are 22 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: