Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of eslint-plugin-react is breaking the build 🚨 #97

Open
greenkeeper bot opened this issue Feb 1, 2020 · 5 comments
Open

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Feb 1, 2020

The dependency eslint-plugin-react was updated from 7.18.0 to 7.18.1.

🚨 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • Format files: null
  • Test (Node 13): There are 1 failures, 0 warnings, and 0 notices.
  • Test (Node 12): There are 2 failures, 0 warnings, and 0 notices.
  • Test (Node 10): null
  • Test (Node 8): null

Commits

The new version differs by 9 commits.

  • 000d6b8 Update CHANGELOG and bump version
  • ffdf69a [Fix] jsx-indent: Does not check indents for JSXText
  • 182b045 [Docs] use markdown-magic to automatically sort all rules alphabetically
  • 45b9d32 [Docs] jsx-props-no-spreading: fix typo to use correct rule
  • f9aee94 [Fix] jsx-props-no-spreading: add support for namespaced jsx components
  • e69b113 [Fix] jsx-no-target-blank: allow rel to be an expression
  • fc6e406 [meta] fix changelog date
  • 50df78f [Fix] sort-comp: | isn’t a valid regex flag; u and s are
  • a7f6a8b [Tests] on node v13

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 1, 2020

After pinning to 7.18.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 2, 2020

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • 37c4ef3 Update CHANGELOG and bump version
  • 3da6eb3 [Fix] jsx-indent: avoid a crash on non-string literals

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 3, 2020

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • 0a717a5 Update CHANGELOG and bump version
  • 8b576be [Fix] jsx-indent: don't check literals not within JSX

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 6, 2020

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 14 commits.

  • e2ed536 Update CHANGELOG and bump version
  • 5959b5f [fix] prefer-stateless-function: avoid crash on ts empty constructor
  • e231f44 [tests] no-unescaped-entities: skip test cases that are now parsing errors in [email protected]
  • 434b45f [Dev Deps] update @types/eslint, @types/estree, @types/node, eslint-plugin-eslint-plugin, eslint-plugin-import, typescript
  • a917dda [Deps] update resolve, xregexp
  • 09608cc [Fix] no-adjacent-inline-elements: avoid a crash
  • b833535 [Fix] no-unused-prop-types: Change the reporting to point to a more accurate node
  • edc5fe2 [New] style-prop-object: Add allow option
  • 9b5d6aa [Fix] self-closing-comp: consider JSXMemberExpression as component too
  • 598277e [New] jsx-pascal-case: Support unicode characters
  • 43e466c [readme] Small visual inconsistency
  • 03edb68 [docs] add react/ prefix to rule name, for consistency
  • b517b9e [Fix] no-unused-prop-types: make markPropTypesAsUsed work with TSEmptyBodyFunctionExpression AST node
  • 66c0d66 [Fix] displayName (but really, propTypes detection): do not crash on empty flow type spreads

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 13, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v7.20.0

Added

Fixed

Docs

Changed

  • [Deps] Move "semver" to devDependencies (#2595 @rajivshah3)
  • [eslint] remove operator-linebreak override (#2578 @golopot)
  • [Tests] button-has-type: ensure no mistakenly allowed identifiers named button/submit/reset (#2625 @golopot)
  • [Tests] displayName: add a test case (#2593 @golopot)
  • [Dev Deps] update @types/eslint, @types/estree, @types/node, @typescript-eslint/parser, coveralls, eslint-config-airbnb-base, eslint-plugin-import, typescript
Commits

The new version differs by 27 commits.

  • 25bf6cc Update CHANGELOG and bump version
  • 2598b1e [Dev Deps] update @types/eslint, @types/estree, @types/node, @typescript-eslint/parser, coveralls, eslint-config-airbnb-base, eslint-plugin-import, typescript
  • f94d851 [Fix] jsx-sort-props: only use localeCompare when case is ignored
  • c481a26 [Docs] Clean up examples in rule docs
  • 88d404d [eslint] remove operator-linebreak override
  • 304590a Merge pull request #2635 from ljharb/eslint7
  • 35030a0 [Tests] fix mistaken error property and add output property
  • 906b474 [New] support eslint v7
  • d66f467 [Fix] jsx-key: add a failing test case for optional chaining
  • da7a045 [Fix] no-unused-state: handle optional chaining
  • 9861469 [New] forbid-component-props/forbid-dom-props: Allow a custom message with forbid props
  • ab28224 [Fix] jsx-pascal-case: Do not consider namespaces when checking for DOM
  • 25b1936 [Fix] jsx-curly-spacing, jsx-no-bind, usedPropTypes util: avoid node.start and node.end
  • db4e471 [readme] Add Rules of Hooks to Other useful plugins section
  • b9d2eb5 [Fix] jsx-no-target-blank: allow no-referrer without noopener by default

There are 27 commits in total.

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants