{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/39bbb350595c4a13aef86ec29f4b748f\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/39bbb350595c4a13aef86ec29f4b748f-683d534a9f88eb24.gif","duration":144.1309,"title":"Resolving Storybook Migration Issues for a Smoother Experience 🚀","description":"I was able to reproduce the storybook migration issue where the command hangs despite passing the 'yes' option to auto-accept everything. It seems we'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."}