Skip to content

Matthew Ronchetto

Maintaining a Gulp Plugin: ESLint

As much as I hate to admit it, I was a rather large fan of and user of JavaScript. To help make sure my spaghetti code isn’t complete.. well.. spaghetti, I use a tool called ESLint to ensure silly mistakes like unclosed brackets and malformed indentations don’t happen. I also use Gulp to run ESLint and a few other tools for me. In other words, it makes life easy. The most popular ESLint plugin for Gulp (at the time of writing) was from Adametry, but was both abandoned and outdated. So, I’ve decided, in true open-source fashion, to fork the repository and give it the love it needs.

Some rather big changes that happened to the plugin:

In February of 2021, I wanted to start to reshape the tool on a fundamental basis by rewriting the plugin in TypeScript and refactoring code to be easily understandable by others. Since then, I’ve been in talks with numerous other developers and decided to ultimately detach myself from the old fork to create not only a better interface with Gulp for ESLint but to possibly make a better tool than ESLint and Gulp as a whole. These hopes and dreams are far into the future, but (were) planned nevertheless.

# Reflecting over gulp-eslint’s corpse

Over time, I grew a victim to the same issue as the original package: it became something I didn’t need anymore with my move to other languages and better solutions. Since I didn’t need it anymore, I didn’t maintain it anymore. To this day, it continues to rot with its dreams of being written entirely in TypeScript.

With hindsight being 20/20 however, I had a terrible idea that other people should work on (or I will some day): native toolings for working with JavaScript. ESLint is written to work using Node; why not a linter written natively to process hundreds of thousands of lines in a blink of an eye, run tests and get responses in a matter of seconds rather than minutes at times, et al., et al. That’s a journey for another day.

Skip to top