<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>zodline — Blog</title>
  <link>https://zodline.dev</link>
  <description>A type-safe CLI parser built with Zod — declare commands, options and args as schemas.</description>
  <atom:link href="https://zodline.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>Type-Safe CLI Parsing with Zod</title>
    <link>https://zodline.dev/blog/type-safe-cli-parsing-with-zod</link>
    <guid isPermaLink="true">https://zodline.dev/blog/type-safe-cli-parsing-with-zod</guid>
    <description>How to describe a command-line interface as a Zod schema so parsing, validation, help output, and TypeScript types all come from one source.</description>
    <pubDate>Thu, 06 Aug 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title>Why Your CLI Parser Should Not Run Your Commands</title>
    <link>https://zodline.dev/blog/separate-cli-parsing-from-execution</link>
    <guid isPermaLink="true">https://zodline.dev/blog/separate-cli-parsing-from-execution</guid>
    <description>Parsing argv and executing a command are two jobs. Splitting them makes commands testable, middleware unnecessary, and error handling ordinary code.</description>
    <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
  </item>
  <item>
    <title>Commander and Yargs Alternatives for TypeScript CLIs</title>
    <link>https://zodline.dev/blog/commander-yargs-alternatives-typescript</link>
    <guid isPermaLink="true">https://zodline.dev/blog/commander-yargs-alternatives-typescript</guid>
    <description>An honest comparison of builder-based CLI parsers and the schema-first approach, and when each one is the right choice.</description>
    <pubDate>Thu, 23 Jul 2026 00:00:00 GMT</pubDate>
  </item>
</channel>
</rss>
