Conversation
| "eslint-plugin-import": "^2.22.1", | ||
| "eslint-plugin-node": "^11.1.0", | ||
| "eslint-plugin-promise": "^4.2.1", | ||
| "eslint-plugin-standard": "^5.0.0" |
There was a problem hiding this comment.
I'm not sure running npx eslint would have any way of knowing about these plugin dependencies anymore
There was a problem hiding this comment.
We can enable them individually (and I initially did --package a --package b ...), however, I couldn't seem to find any functional difference from removing them?
There was a problem hiding this comment.
Would have to add a violation to one of the rules supplied by one of these plugins to see any difference
There was a problem hiding this comment.
That is what I tried yes.
There was a problem hiding this comment.
In the latest run
ESLint couldn't find the config "standard" to extend from.
|
@oliver-sanders Poke - what's the status of this one? |
|
Work not in progress. Would be good to do, one day... |
3 participants
We really don't need to maintain an eslint lock file, we just need a vaguely up-to-date version.