ESLint Fix Patterns

How to resolve specific ESLint errors in this project.

no-void

no-void reports void in expression position (an arrow body such as () => void navigate(...)); a void expr; statement is allowed. In an event handler, prefer an async handler that awaits the promise. Any other fire-and-forget statement (an effect body, a module-level call) uses void, never .catch(() => {}).

// BAD
const handleClickNavigate = () => void navigate('/path');

// GOOD
const handleClickNavigate = async () => {
  await navigate('/path');
};

canonical/export-specifier-newline vs prettier conflict

Use inline export const declarations instead of a grouped export { ... } statement to avoid circular fix warnings between these two rules.

// BAD, causes circular fix between prettier and canonical
export {DAYS, DURATIONS, FITNESS_GOALS};

// GOOD, declare with export directly
export const DAYS = ['mon', 'tue'] as const;
export const DURATIONS = [15, 30, 45] as const;
export const FITNESS_GOALS = ['weight_loss'] as const;

no-shadow trailing underscores

no-shadow has no autofix: rename the inner binding to a descriptive name, not a trailing _.

sonarjs/deprecation

Never suppress with eslint-disable. Always fix the underlying deprecation.

Common case: Zod v4 deprecated z.string().email() in favor of z.email().

// BAD, suppressing the warning
// eslint-disable-next-line sonarjs/deprecation
email: z.string().email(),

// GOOD, use the non-deprecated API
email: z.email(),

you-dont-need-lodash-underscore/*

Use native JavaScript instead of lodash/underscore equivalents.

// BAD
import _ from 'lodash';
const first = _.find(items, (item) => item.active);
const names = _.map(items, (item) => item.name);

// GOOD
const first = items.find((item) => item.active);
const names = items.map((item) => item.name);

Unawaited user-event calls

userEvent from storybook/test is async in a play function, always await it.

// BAD
userEvent.click(button);

// GOOD
await userEvent.click(button);

Raw DOM property checks

Use the jest-dom matchers storybook/test re-exports instead of raw DOM property checks.

// BAD
expect(input.value).toBe('hello');
expect(checkbox.checked).toBe(true);
expect(el.textContent).toBe('Hello');

// GOOD
expect(input).toHaveValue('hello');
expect(checkbox).toBeChecked();
expect(el).toHaveTextContent('Hello');