<?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/bbe81b692a2640a8b09f5991efbb1460&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bbe81b692a2640a8b09f5991efbb1460-35c8197c3f8f2897.gif</thumbnail_url><duration>357.6126</duration><title>Simplifying Diagnostics with VADER 🚀</title><description>In this video, I introduce VADER, an open-source diagnostics collection tool designed to help developers gather crucial information about their code environments. I demonstrate how users can create and share scripts that capture relevant data, reducing the back-and-forth communication typically required to troubleshoot issues. I also highlight some of the commands available within VADER, such as checking Node and NPM versions. Please take a look and let me know your thoughts on how we can enhance this tool further!</description></oembed>