Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
eslint-config-eslint needs a major version release
See original GitHub issueTSC Summary: Our internal ESLint configuration, package “eslint-config-eslint”, hasn’t been updated on npm for nine months. This means that other ESLint repos which use it aren’t getting the benefits of recent changes to that configuration.
Since changing a config is probably a breaking change for consumers (we consider it as such with eslint:recommended, after all), I believe we should publish a major version.
TSC Question: Should we publish a new major version for eslint-config-eslint?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Now that https://github.com/eslint/eslint/issues/7725 is closed and we’ve added all the rules in https://github.com/eslint/eslint/issues/6407, I think we’re ready to do this (unless anyone has other rules that they’d like to add).
Fine by me. We might want to decide what we’re doing about
comma-dangle(https://github.com/eslint/eslint/issues/7725) first though.