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 issueIt’s up to you —@ljharb—, but if you’d like, you’re welcome to transfer this repository 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.
Again, totally up to you. I just want you to know we appreciate all you’ve done and you’re welcome to join the organization if you like.
Issue Analytics
- State:
- Created a year ago
- Comments:10 (10 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
As I said: there’s no separate ESLint community collective, so all new sources of funding would go to the main collective anyways.
I’m sorry, I thought it was, as you’re the only one mentioned in sponsors & seems to be the only active person working on these repos.
Like I said before: it’s totally up to you to join the official community org if you want to.
If you have any other concerns/questions/remarks, please let me know.