Loving the fact that their flat config compatibility package has 83% the number of weekly downloads compared to their main package. It was pretty obvious years

Loving the fact that their flat config compatibility package has 83% the number of weekly downloads compared to their main package. It was pretty obvious years ago that eslint messed up how package names are referenced in configs, and how they're resolved. Did it really require such a big change that affects the whole ecosystem? Microsoft seemed to have a pretty good solution with https://www.npmjs.com/package/@rushstack/eslint-patch https://www.npmjs.com/package/@rushstack/eslint-patch