For nearly three years now, both teams have been working on solving the same types of issues: how to share configurations, how to autofix some problems, and how to enable the respective ecosystems to grow and thrive. We’ve been doing a lot of the same work in parallel, and recently the teams met to talk about that. We all came to the conclusion that it would be better to be one team, working together on solving these problems, rather than continuing to compete with one another.
Below you’ll find more details about how we’ll move forward as a single team and our plans for both JSCS and ESLint.
Welcoming the JSCS Team
I’m happy to announce that, effectively immediately, the JSCS team is now part of the ESLint team. I’d like to invite everyone to welcome Marat Dulin, Oleg Gaidarenko, Mike Sherov, Alexej Yaroshevich, and Henry Zhu, and we’re looking forward to working with them all. All of the JSCS team members will be joining ESLint as committers (based on our governance policy) for appreciation of their work on JSCS.
Joel Kemp has decided to focus on other work and won’t be joining ESLint. I, and the rest of the team, would also like to thank Joel for his many contributions to JSCS over the years.
If you’re a current JSCS user, I strongly urge you to upgrade to 3.0.0 and report your experience. The JSCS team will continue to work on JSCS in the near-term, fixing bugs as they are reported.
Making ESLint Work for JSCS Users
We recognize that there is a large and vibrant JSCS user base, and as such, the first goal of the combined ESLint/JSCS team is to make the transition to ESLint easy for JSCS users. To that end, our immediate-term plan includes the following tasks:
- Identifying rules that exist in JSCS but are missing in ESLint and creating as many of those rules as we can. (#5856)
- Incorporating a way to convert
.eslintrcfiles with the goal of having a single command to do this automatically. (#5857)
- Creating ESLint shareable configs for the most popular JSCS presets. (#5858)
- Expanding ESLint’s autofixing capabilities to fix more problems and try, as much as is possible, to approach the level of autofixing available in JSCS 2.x.
- Write documentation to guide JSCS users through transitioning to ESLint. (#5859)
Check out our milestone on the tasks above here.
We expect this effort to take several months, and as such, we still encourage current JSCS users to upgrade to JSCS 3.0.0 and provide feedback to the team. We’ll announce when all of the changes necessary to support JSCS users in ESLint are complete and will start encouraging JSCS users to switch to ESLint at that time.
The Future is Bright