eslint-plugin-unicorn

I work on a project where we recently heavily pivoted into AI assisted feature development and without a extremely defensive/aggressive lint config and test coverage near ~80% most of these developments would be quiet impossible. `no-reflect-get` is definitely one I'd adopt, claude LOVES `Reflect.get` for some reason A lot of the lint rules in this repo remind me of https://github.com/sindresorhus/eslint-plugin-unicorn, I can't wait until oxlint has plugin support so I can move over to it.

I am a typescript dev and I like reduce but also feel like I am the exception. The standard linter plugin eslint-plugin-unicorn even has a rule "no-array-reduce" that is part of the recommended config, which means most people using this plugin will have no reduce in their codebases: https://github.com/sindresorhus/eslint-plugin-unicorn/blob/m...

Having too many options leads to a lot of bikeshedding as the whole ecosystem ends up fragmenting and disagreeing with each other. It’s one of things I really dislike about JS compared to something like Go. Personally, I stick to opinionated rulesets such as Standard[1], AirBnb[2] and Unicorn[3] since you won’t spend hours tweaking and selecting new rules. [1] https://standardjs.com/ [2] https://github.com/airbnb/javascript [3] https://github.com/sindresorhus/eslint-plugin-unicorn

I would recommend using eslint and the following rule : https://github.com/sindresorhus/eslint-plugin-unicorn/blob/m... eslint-plugin-unicorn has a lot of great rules, some are opinionated but you don't have to use all the rules.