-
Notifications
You must be signed in to change notification settings - Fork 2
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
ESLint v8 Support @ijsto/eslint-config #10
Comments
Hello @rtritto thank you for reporting this, until early/mid November it may be a little bit tricky to get to this, but will look into this as soon as possible. If anyone else is experiencing this issue, please add to this thread. 🙏🏼 |
+1 same here i've no problem with version
Step to reproduceyarn eslint ./**.js result
|
SOLUTION / TRACKERTo resolve this issue, we need to wait for the rest of the ecosystem to release support for ESLint V8. ## Progress Tracker
|
Support for ESLint v8 in eslint-plugin-import was relased in v2.25.0. |
SOLUTION/TRACKER is updated with references. |
The latest version To update you can use npx install-peerdeps --dev @ijsto/eslint-config@latest If you run into any bug, please open a new issue and it will be addressed with a patch version. |
After install ( ➤ YN0060: │ test-eslint@workspace:. provides eslint (pf3766) with version 8.2.0, which doesn't satisfy what @ijsto/eslint-config and some of its descendants request
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: test-eslint@workspace:. provides eslint@npm:8.2.0 with version 8.2.0, which doesn't satisfy the following requirements:
➤ YN0000: @ijsto/eslint-config@npm:4.2.7 [0f3ca] → ^7.25.0 || ^8.0.0 ✓
➤ YN0000: eslint-config-airbnb-base@npm:14.2.1 [943ee] → ^5.16.0 || ^6.8.0 || ^7.2.0 ✘
➤ YN0000: eslint-config-airbnb@npm:18.2.1 [41e81] → ^5.16.0 || ^6.8.0 || ^7.2.0 ✘
➤ YN0000: eslint-config-prettier@npm:8.3.0 [41e81] → >=7.0.0 ✓
➤ YN0000: eslint-plugin-es@npm:3.0.1 [9598e] → >=4.19.1 ✓
➤ YN0000: eslint-plugin-import@npm:2.25.3 [41e81] → ^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 ✓
➤ YN0000: eslint-plugin-jsx-a11y@npm:6.5.1 [41e81] → ^3 || ^4 || ^5 || ^6 || ^7 || ^8 ✓
➤ YN0000: eslint-plugin-node@npm:11.1.0 [41e81] → >=5.16.0 ✓
➤ YN0000: eslint-plugin-prettier@npm:4.0.0 [41e81] → >=7.28.0 ✓
➤ YN0000: eslint-plugin-react-hooks@npm:4.3.0 [41e81] → ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 ✓
➤ YN0000: eslint-plugin-react@npm:7.27.0 [41e81] → ^3 || ^4 || ^5 || ^6 || ^7 || ^8 ✓
➤ YN0000: Note: these requirements start with @ijsto/eslint-config@npm:4.2.7 [0f3ca] Plugins that need support to Eslint v8:
FYI @ScottAgirs |
@rtritto thank you for reporting this. Strange, I cannot reproduce this on my end, could you please share your If anyone else is experiencing same issue, please chime in |
My package.json only have |
@ScottAgirs I saw the commit, you should never change directly version of a dependency in package.json, you must use upgrade/update option command of the package manager (npm/yarn etc). |
Hey @rtritto thanks again for the pointers - duly noted! I have few improvements in mind for this package, including proper semver release mechanism, that surely is no excuse not to do things in a proper way! :) If you're open to contributing and suggesting some improvements, please ping me on twitter.com/scottagirs - would love to chat! Also please feel free to open a PR, if you find any areas for improvements/fixes. |
eslint
version 8 was released and I got warning on install step.Step to reproduce
yarn init -y
yarn set version berry
yarn add eslint @ijsto/eslint-config
Result
Actual
Expect
No warning in log
Versions
eslint
: 8.0.0@ijsto/eslint-config
: 4.1.6This issue is confirmed and is a composite issue which requires for a wider ecosystem support for ESLint v8.
We are aware of this, we will monitor and update the codebase to provide support to ESLint v8 as soon as it's possible.
Please see below for a tracker of the current progress (will be updated incrementally).
The text was updated successfully, but these errors were encountered: