-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Pre-work to update to ESLint 8 #5699
Conversation
@mattxwang Thank you for creating this PR! 😄 I try removing $ npm rm eslint-plugin-jest
...
$ npm ls eslint-plugin-jest
stylelint@14.0.1 /Users/koba/git/stylelint/stylelint
└─┬ eslint-config-stylelint@15.0.0
└── eslint-plugin-jest@25.2.3
$ npm run lint:js -- --no-cache
> stylelint@14.0.1 lint:js
> eslint . --cache --max-warnings=0 "--no-cache" |
Yeah, I had the same issue locally it worked without this, installing resolved it for me also /shrug
TypeError: Failed to load plugin 'jest' declared in 'package.json » eslint-config-stylelint': Class extends value undefined is not a constructor or null
Referenced from: /home/runner/work/stylelint/stylelint/node_modules/eslint-config-stylelint/index.js |
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.
Per my comment #5699 (comment) I'm happy to approve this and land this as-is, we can revisit removing the eslint-plugin-jest
plugin later
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.
@ntwb Ah, I see. Thanks for the feedback! 😄
LGTM 👍🏼
Thanks everyone! I can also try to see if removing |
Not an issue, but part of the discussion in #5645.
This PR slightly took on scope creep (from the initial ask to just update
eslint-shared-config
to major version 15. Here's my thought process:eslint-plugin-jest
. I could resolve this by manually reinstalling it as a dev dependency. I'm not sure if this is the right move; if it isn't, let me know and I can move this commit out of the PR.jest/prefer-to-be
rule, which was a simple find-and-replace.Let me know if we'd prefer dependabot to handle. I'm using node 16 to generate the new
package-lock
, and we stay on lockfile v2.