Update dependency @ijsto/eslint-config to v3.0.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@ijsto/eslint-config	3.0.1 -> 3.0.2

---

Release Notes

ijsto/eslint-config

v3.0.2: 3.0.2

Compare Source

With this release we deprecate prettier/react as it's included in general prettier configuration. #​5 @​valoricDe

Fixes #​4

To update run

yarn add @​ijsto/eslint-config@latest

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: clipper-gui@0.0.1
npm ERR! Found: babel-eslint@10.1.0
npm ERR! node_modules/babel-eslint
npm ERR!   dev babel-eslint@"10.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer babel-eslint@"^9.0.0" from @ijsto/eslint-config@3.0.2
npm ERR! node_modules/@ijsto/eslint-config
npm ERR!   dev @ijsto/eslint-config@"3.0.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-05-05T15_45_48_790Z-debug.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: clipper-gui@0.0.1
npm ERR! Found: babel-eslint@10.1.0
npm ERR! node_modules/babel-eslint
npm ERR!   dev babel-eslint@"10.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer babel-eslint@"^9.0.0" from @ijsto/eslint-config@3.0.2
npm ERR! node_modules/@ijsto/eslint-config
npm ERR!   dev @ijsto/eslint-config@"3.0.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-05-07T15_03_22_675Z-debug.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.