Are all the disabled rules and warnings in the .eslintrc intentional?

I didn't have much use for them when it was just me working on the code. I'll have to re-enable most of these as part of the Issue.

then why not just disable eslint?

It's important to me that the code remains as easy as possible to maintain, especially as the project grows. I'd like to get more people involved improving the codebase as well, not having a standard style would make that difficult.

The results of me being lazy about enabling the rules are inconsistencies across the codebase now. How can I ask others to maintain quality if I can't follow the rules myself? And If I do get enough people to contribute, one of the worst things that could happen are arguments over code-style, which I'd like to avoid.

No I'm asking why you used eslint before if you disable all those rules

Oh, sure.

If you take a look at the currently enabled config, it's already pretty useful; it just doesn't enforce a few style rules I have done out of habit. It helped me catch silly bugs(undefined variables etc.,), and keep stuff like console.logs and debugger statements out of builds.

Going to punt on the type naming rule. Maybe will be done at a later point.