extract-default-non-primitive-parameter-to-constant

Memoization fails because non-primitive default parameters create new object instances on each render, breaking referential equality checks in React.memo. Extracting these defaults into external constants stabilizes references and prevents unnecessary re-renders.

To fix memoization breaking, extract the default onClick handler into a constant outside the component. This ensures the default prop maintains referential equality across renders when the handler is not explicitly provided.

The best way to stabilize default props is to extract non-primitive default values into module-level constants. This prevents redefining instances on every render and ensures consistent referential equality for React.memo checks.

Yes, defining a default object parameter inside a React component causes re-renders because it generates a new memory reference on each render. Moving the default value to a constant outside the component resolves this performance issue.

You need to extract default parameters to constants when using memoized React components with optional non-primitive props. This optimization is required when default objects, arrays, or functions are redefined per render, failing React.memo referential equality checks.