<?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/3995cb910caf4f3b85113ff4e957d2d9&quot; frameborder=&quot;0&quot; width=&quot;1670&quot; height=&quot;1252&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1252</height><width>1670</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1252</thumbnail_height><thumbnail_width>1670</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3995cb910caf4f3b85113ff4e957d2d9-5a83323557ed281a.gif</thumbnail_url><duration>508.158</duration><title>Easier package cleanup in Glide</title><description>In this video, I discuss my recent efforts to clean up our package dependencies, particularly focusing on removing unnecessary dependencies from Common Core. I demonstrate a utility I&apos;ve developed that automates the process of resolving imports and deduping them, which significantly reduces the manual effort required. I also share insights on how this utility works and the challenges I faced with parsing imports and exports. I encourage you to check out the utility and consider how it might help in your own work.

https://github.com/glideapps/glide-code-utility</description></oembed>