← Public packages
@kentcdodds/cloudflare-connect-personal-software-ecosystem
I Built Your Personal Software Ecosystem: Kent C. Dodds's Cloudflare Connect 2026 lightning talk deck (Reveal.js). How Kody gives every user one of everything on Cloudflare.
Files
<section id="packages" data-slide="packages" data-title="Code composes">
<h2>Code composes</h2>
<pre><code class="language-typescript">import bondAreaShades from
"kody:@kentcdodds/home-controls/bond-area-shades"
import runMorningBriefing from
"kody:@kentcdodds/morning-briefing"
import { getEpisode } from "kody:@kentcdodds/transistor"
export default async function main(input) {
const shades = await bondAreaShades({ area: "back", action: "close" })
const briefing = await runMorningBriefing({ dryRun: true })
const episode = await getEpisode({ episodeId: input.episodeId })
return { shades, briefing, episode }
}</code></pre>
<p class="pkg-links">
<a href="https://kody.codes/@kentcdodds/home-controls">home-controls</a>
<a href="https://kody.codes/@kentcdodds/morning-briefing">morning-briefing</a>
<a href="https://kody.codes/@kentcdodds/transistor">transistor</a>
</p>
<aside class="notes">
Solution: publish an export. You import it. You compose it. Real kody:* imports:
home-controls closes the back shades, the same export search found earlier. Any host
that can execute can call what you already saved. Next: how that import actually
lands in an isolate.
</aside>
</section>