-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Release 15.0.0 #152
Comments
Unfortunately, these changes don't fix the downstream issues. We now get the following when using
It seems something is up with the plugin resolution, and more investigation is needed. I'm calling it a day, though. Feel free to pick this up. |
I'm not sure if I think this is a similar issue to the downstream one in the shared config - see mysticatea/eslint-plugin-eslint-comments#63 Interestingly, they have the same core maintainer, the same person who filed the issue for ESLint 8 support, and the same author of the draft PR. In the meantime, maybe we need to halt moving towards ESLint 8? Or, alternatively, ping the author, fork and update, etc. |
The plugin resolution issue is present for ESLint 7 too. See the standard config CI logs: https://github.com/stylelint/stylelint-config-standard/runs/3967292608?check_suite_focus=true I don't know what's causing it. Perhaps somethings to do with NPM@8. It'll need investigating. I think our next steps are:
I'm away and offline for the next few days, so release in my absence if the issue gets resolved. |
Ah, good catch. I may have some time this weekend so I can see what I can do! |
This is possibly related to eslint/eslint#15079 Going to merge #153 and test, possibly do a pre-release of this package for testing Released: https://www.npmjs.com/package/eslint-config-stylelint/v/next (v15.0.0-0) https://github.com/stylelint/eslint-config-stylelint/releases/tag/15.0.0-0 |
Confirmed: Using Before: ~/Code/stylelint/stylelint-config-standard main !2 npm run lint ✔
> [email protected] lint
> npm-run-all --parallel lint:*
> [email protected] lint:md
> remark . --quiet --frail --ignore-path .gitignore
> [email protected] lint:formatting
> prettier . --check
> [email protected] lint:js
> eslint . --ignore-path .gitignore
Oops! Something went wrong! :(
ESLint: 8.1.0
ESLint couldn't find the plugin "eslint-plugin-eslint-comments".
(The package "eslint-plugin-eslint-comments" was not found when loaded as a Node module from the directory "/Users/netweb/Code/stylelint/stylelint-config-standard".)
It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
npm install eslint-plugin-eslint-comments@latest --save-dev
The plugin "eslint-plugin-eslint-comments" was referenced from the config file in "package.json » eslint-config-stylelint".
If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.
ERROR: "lint:js" exited with 2. After: ~/Code/stylelint/stylelint-config-standard main !2 npm run lint ✔ 6s
> [email protected] lint
> npm-run-all --parallel lint:*
> [email protected] lint:md
> remark . --quiet --frail --ignore-path .gitignore
> [email protected] lint:formatting
> prettier . --check
> [email protected] lint:js
> eslint . --ignore-path .gitignore
Checking formatting...
All matched files use Prettier code style! |
Closing this out as fixed, I've regenerated the
I'll look at our repos a little later today |
I meant to open a pull request, but forgot to branch.
Commit here: 62ac183
Clean CI: https://github.com/stylelint/eslint-config-stylelint/actions/runs/1369217773
Need a couple of pairs of eyes to check it over before releasing.
Ref: stylelint/stylelint#5624 (comment)
The text was updated successfully, but these errors were encountered: