wp-interactivity-api

To debug WordPress Interactivity API directives, you must diagnose how data-wp-interactive, data-wp-on--*, and data-wp-bind--* are applied across frontend and editor surfaces to ensure proper hydration and consistent interactions.

State initialization in @wordpress/interactivity stores works by identifying the state shape, actions, and event handlers to drive user interactions, ensuring the initial server-side rendered HTML mirrors client-side state to reduce layout shifts.

The best way to integrate Interactivity API directives within block.json is by configuring the block viewScriptModule and applying safe integration guidelines to ensure proper directive processing and hydration within block contexts.

Yes, you can use WordPress Interactivity API directives in non-block contexts like themes and plugins by following practical integration steps that ensure correct directive processing and state hydration across frontend and editor surfaces.

Layout shifts occur after hydration when server-side rendering does not correctly mirror the initial client-side state, requiring you to validate your server-side rendering and hydration strategies to align the HTML output.