<?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/7c3ad6a27a6b48d0b652cec248f51bbd&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/7c3ad6a27a6b48d0b652cec248f51bbd-c9ba36128153a4b8.gif</thumbnail_url><duration>241.2678</duration><title>Benchmarking TS Project Reference Changes 📊</title><description>I conducted benchmarking on TS project reference changes, focusing on speed differences and other benefits of project reference versus without. In the best case scenario, there was a 3x speed up, reducing build times significantly. Proper project reference setup also resolves issues with finding all references in VS Code. I recommend considering these changes for improved efficiency.</description></oembed>