<?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/84a7098b3d1e4a819bd598ad7fc3ae7f&quot; frameborder=&quot;0&quot; width=&quot;1378&quot; height=&quot;1033&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1033</height><width>1378</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1033</thumbnail_height><thumbnail_width>1378</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/84a7098b3d1e4a819bd598ad7fc3ae7f-6fb5e818178edcac.gif</thumbnail_url><duration>1133.58</duration><title>tsc issue reproduction with recommended monorepo tsconfig setup, and project opting out of composite</title><description>In the video, I explain how TSC as a CLI tool can benefit from NX&apos;s additional features like deterministic hashing and distributable task execution to scale a monorepo efficiently. I introduce the concept of synchronizing project graphs for enhanced task execution and configuration file management. Viewers are encouraged to understand the seamless integration of NX with TypeScript configurations and the benefits it offers in managing monorepos effectively.</description></oembed>