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.
Invitation to move to official `eslint-community` org
See original GitHub issueWe would love to have this repo added to the official @eslint-community organization on GitHub.
As you can read in the ‘@eslint-community GitHub organization’ RFC, the goal of this new org is to have a place where community members can help ensure widely depended upon ESLint related packages stay up to date with newer ESLint releases and doesn’t hold the wider community back without depending on one person’s GitHub/npm account.
Since this plugin is currently maintained by the ESLint TSC, it’s taking time away from the main repo & responsibilities from the team. That’s why we think it’s a good idea to transfer this repo to a better home, so you’re welcome to transfer this repository to the new org.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 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
Yeah, I don’t think it’s worth moving eslint-community under Open JS. There’s not a lot of value there.
@MichaelDeBoey when other folks extract code from our repo and set up a different repo (which they are allowed to do by the license), that becomes a separate project that can be run separately. It’s the transferring of an existing repo that brings over all the overhead.
@snitin315 my understanding is that the Open JS CLA checker applied to every repo in an org, you can’t just pick one or two.