<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/e295d9eccbc6496e8f6d55f1b878f795&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/e295d9eccbc6496e8f6d55f1b878f795-00001.gif</thumbnail_url><duration>354</duration><title>Add Interactivity API runtime by DAreRodz · Pull Request #49994 · WordPress/gutenberg - 21 April 2023</title><description>Hey there! In this Loom, I wanted to explain the changes we made to the interactivity API in core blocks and how you can start using it. We moved all the interactivity API files to a specific folder and modified the webpack configuration to create two chunks - one for node modules and another for interactive blocks. We also registered the scripts with their respective handles and added the defer attribute for interactivity scripts. If you want to use the interactivity API in one of the core blocks, check out this commit where we removed the changes we made to test everything is working. We also added an endpoint for the image block and defined it in a separate effect. To use it, we need to add attributes with directives and use islands because the only parts that are hydrated are islands. Hope this helps!</description></oembed>