-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix(deps): update dependency @typescript-eslint/eslint-plugin to v6 #2844
fix(deps): update dependency @typescript-eslint/eslint-plugin to v6 #2844
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ae5b61c
to
cd5c1b1
Compare
cd5c1b1
to
a9045f8
Compare
a9045f8
to
9964cfb
Compare
9964cfb
to
1eb5215
Compare
1eb5215
to
b921a2a
Compare
b921a2a
to
1b986e6
Compare
I think we need to wait until the next eslint-config-next version is released track: vercel/next.js#52848 |
1b986e6
to
b152963
Compare
b152963
to
379fae5
Compare
379fae5
to
99083f1
Compare
99083f1
to
85e9232
Compare
85e9232
to
b3cb4b5
Compare
b3cb4b5
to
fdb280c
Compare
fdb280c
to
96775ae
Compare
c5b20e9
to
c1fc83b
Compare
b6e06fd
to
80cb20d
Compare
80cb20d
to
730b2bf
Compare
d63ac51
to
2ef0ca7
Compare
2ef0ca7
to
83dc00f
Compare
83dc00f
to
fe8736c
Compare
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
Edited/Blocked NotificationRenovate 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. |
fe8736c
to
55c3d83
Compare
@@ -5,7 +5,8 @@ | |||
"main": "eslint-config-custom.js", | |||
"license": "MIT", | |||
"dependencies": { | |||
"@typescript-eslint/eslint-plugin": "5.62.0", | |||
"@typescript-eslint/eslint-plugin": "6.2.1", | |||
"@typescript-eslint/parser": "6.2.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The was causing the issue: we needed to update the parser.
'plugin:@typescript-eslint/recommended-type-checked', | ||
'plugin:@typescript-eslint/stylistic-type-checked', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're talking about a breaking change update here.
As it can be looked in their docs they changed the way typescript-eslint
is configured.
'@typescript-eslint/array-type': 'off', | ||
'@typescript-eslint/consistent-type-definitions': 'off', | ||
'@typescript-eslint/prefer-nullish-coalescing': 'off', | ||
'@typescript-eslint/non-nullable-type-assertion-style': 'off', | ||
'@typescript-eslint/no-redundant-type-constituents': 'off', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're also talking about some new rules. I'm trying to disable them here just to move forward with it but we might want want to consider on enabling them and fix any issues in the future.
Now, I'm saying trying because there's some weird behaviour. Even though I'm disabling some rules in this file, the eslint rules to are still breaking. That's happening for old and new rules.
E.g: We're disabling @typescript-eslint/no-explicit-any
in this file which is extended by ui
, onboarding
and store
eslint configurations. However, eslint still complains about it.
The same happens for the new rules as well. Any hints on why is that?
@alebedev @robinandeer
55c3d83
to
fe4aae9
Compare
@@ -76,15 +89,5 @@ module.exports = { | |||
'@typescript-eslint/no-var-requires': 'off', | |||
}, | |||
}, | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alebedev Let me know if that makes sense to be removed or if there something that I'm not foreseeing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was necessary evil, glad it works without it now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job, let's merge!
fe4aae9
to
aeaf187
Compare
This PR contains the following updates:
5.62.0
->6.2.1
Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.2.1
Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.2.0
Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.1.0
Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.0.0
Compare Source
Bug Fixes
exports
field in package.json files (#6550) (53776c2)chore
Features
rule-tester
(#6777) (2ce1c1d)RuleTester
in/utils
in favour of the new/rule-tester
package (#6816) (c33f497)BREAKING CHANGES
You can read about our versioning strategy and releases on our website.
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), 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.
This PR has been generated by Mend Renovate. View repository job log here.