2026-11-02 09:05 UTC
The recommended ESLint rules catch most of the bad stuff, and these days this is all you need in your ESLint config to enable them:
import {defineConfig} from 'eslint/config';
import js from '@eslint/js'
export default defineConfig([
js.configs.recommended,
];
There’s one use case where == is still commonly used: == null matches both null and undefined. Lint rules that block == usually allows the null case as an exception.
Replies (2)
-
@Venator@lemmy.nz 2026-11-02 09:32
I wonder how much bandwidth is wasted on the extra =, since it survives minification 😅
-
@BradleyUffner@lemmy.world 2026-11-02 12:37
So you’re saying the jank had become structural?