<?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/39bbb350595c4a13aef86ec29f4b748f&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/39bbb350595c4a13aef86ec29f4b748f-683d534a9f88eb24.gif</thumbnail_url><duration>144.1309</duration><title>Resolving Storybook Migration Issues for a Smoother Experience 🚀</title><description>I was able to reproduce the storybook migration issue where the command hangs despite passing the &apos;yes&apos; option to auto-accept everything. It seems we&apos;re passing an unnecessary environment variable, which causes the hang-up. When I removed the storybook project route option, the migration worked correctly, so I recommend we eliminate that variable to unblock users. I believe we should backport this change as well. Please let me know if you have any questions or need further clarification.</description></oembed>