An in-range update of eslint-plugin-react is breaking the build π¨
Closed this issue Β· 1 comments
The devDependency eslint-plugin-react was updated from 7.16.0
to 7.17.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v7.17.0
Added
jsx-no-target-blank
: addallowReferrer
option (#2478 @eps1lon)jsx-handler-names
: addcheckLocalVariables
option (#2470 @aub)prop-types
: Support Flow Type spread (#2446 @moroine)jsx-props-no-spreading
: addexplicitSpread
option to allow explicit spread of props (#2449 @pawelnvk)jsx-no-target-blank
: warn ontarget={'_blank'}
expressions (#2451 @timkraut)
Fixed
sort-prop-types
,jsx-sort-default-props
: disable broken autofix (#2505 @webOS101)no-typos
: improve report location (#2468 @golopot)jsx-no-literals
: trim whitespace forallowedStrings
check (#2436 @cainlevy)jsx-curly-brace-presence
: Fix filter of undefined error with whitespace inside jsx attr curlies (#2460 @dustinyoste)no-render-return-value
: should warn when used in assignment expression ([#2462][] @jichu4n)jsx-curly-brace-presence
: allow trailing spaces in literal (#2448 @doochik)
Changed
- [Deps] update
jsx-ast-utils
,object.fromentries
,resolve
- [eslint] fix func-names and change object-shorthand to 'always' (#2483 @golopot)
- [Docs]
jsx-first-prop-new-line
: Fix documentation formatting (#2489 @pjg) - [Docs]
prop-types
: Update 'skipUndeclared' in rule options (#2504 @cjnickel) - [Docs]
jsx-first-prop-new-line
: fix wrong rule name (#2500 @zgayjjf) - [eslint] enable eslint-plugin-eslint-plugin (#2469 @golopot)
- [Docs]
jsx-props-no-multi-spaces
: suggest using core rule instead (#2463 @golopot) - [Docs]
jsx-first-prop-new-line
: add rule options (#2465 @SerdarMustafa1) - [Docs]
jsx-no-target-blank
: Add section about overriding for trusted links (#2438 @aschriner) - [Docs] fix typo (#2453 @cainwatson)
- [Docs]
no-unused-prop-types
: clean up prose (#2273 @coryhouse) - [Docs]
jsx-no-bind
: add section about React Hooks (#2443 @kdex)
Commits
The new version differs by 26 commits.
027ebd9
Update CHANGELOG and bump version
89911de
[Deps] update
jsx-ast-utils
,object.fromentries
,resolve
cfef664
[Dev Deps] update
@types/eslint
,@types/estree
,@types/node
,coveralls
,typescript
d3b5d71
[New]
jsx-no-target-blank
: addallowReferrer
option83ac4c0
[eslint] fix func-names and change object-shorthand to 'always'
225b433
[Docs]
jsx-first-prop-new-line
: Fix documentation formatting62df1dd
[Docs]
prop-types
: Update 'skipUndeclared' in rule options87d4cab
[Docs]
jsx-first-prop-new-line
: fix wrong rule name55b605f
[Fix]
sort-prop-types
,jsx-sort-default-props
: disable broken autofix71c7d01
[Tests] temporarily pin eslint 6 tests to v6.6
8093565
[New]
jsx-handler-names
: addcheckLocalVariables
option5be539b
[Fix]
no-typos
: improve report locationd9d2193
[eslint] enable eslint-plugin-eslint-plugin
39e4396
[Docs]
jsx-props-no-multi-spaces
: suggest using core rule instead9e4ad21
[Docs]
jsx-first-prop-new-line
: add rule options
There are 26 commits in total.
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 π΄
After pinning to 7.16.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.