wp-interactivity-api

To debug WordPress Interactivity API hydration gaps, inspect the server-rendered HTML for missing data-wp-interactive attributes and ensure your viewScriptModule correctly initializes the client store. Aligning server-side and client state prevents hydration mismatches.

Implement WordPress Interactivity API directives by defining data-wp-interactive and data-wp-on--* attributes in your block's HTML, then registering the viewScriptModule in block.json to handle store, state, and actions patterns for frontend interactivity.

Initialize derived state for WordPress blocks using the PHP helpers wp_interactivity_state() and wp_interactivity_data_wp_context(). These functions pass server-side data directly into the Interactivity API store before frontend hydration occurs.

Yes, the WordPress Interactivity API fully supports server-side rendering. You can use PHP helpers to inject context and state into the rendered HTML, ensuring interactive blocks receive proper data before client-side hydration begins.

The best way to troubleshoot a non-working WordPress interactive block is to triage the directives, viewScriptModule usage, and hydration gaps. Describe your block.json settings and server-rendered HTML to pinpoint corrective steps.