<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Logan Jenkins</title>
    <description>The latest articles on DEV Community by Logan Jenkins (@logan_works).</description>
    <link>https://dev.to/logan_works</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210622%2Fbc664f96-d3d0-4e38-81d4-a1c9c8d6c3da.jpg</url>
      <title>DEV Community: Logan Jenkins</title>
      <link>https://dev.to/logan_works</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/logan_works"/>
    <language>en</language>
    <item>
      <title>Vite config that survived three projects</title>
      <dc:creator>Logan Jenkins</dc:creator>
      <pubDate>Wed, 28 Oct 2026 04:38:41 +0000</pubDate>
      <link>https://dev.to/logan_works/vite-config-that-survived-three-projects-1853</link>
      <guid>https://dev.to/logan_works/vite-config-that-survived-three-projects-1853</guid>
      <description>&lt;p&gt;I've copied the same Vite config into three projects now, so it's probably worth writing down.&lt;/p&gt;

&lt;p&gt;What's in it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;server.proxy&lt;/code&gt; for the API, so no CORS in dev&lt;/li&gt;
&lt;li&gt;Path aliases (&lt;code&gt;@/&lt;/code&gt;) matching tsconfig&lt;/li&gt;
&lt;li&gt;A tiny plugin that fails the build on &lt;code&gt;console.log&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Manual chunks for the two libraries that never change&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last one gave the biggest win: the vendor chunk is cached and the app chunk stays small.&lt;/p&gt;

&lt;p&gt;I keep a &lt;code&gt;vite.config.ts&lt;/code&gt; template in a gist and update it when I learn something. The console.log plugin has saved me from shipping debug noise more than once.&lt;/p&gt;

&lt;p&gt;Learning Kotlin Multiplatform next, mostly out of curiosity about sharing logic across platforms.&lt;/p&gt;

</description>
      <category>vite</category>
      <category>typescript</category>
      <category>frontend</category>
    </item>
    <item>
      <title>A small React pattern that removed half our prop drilling</title>
      <dc:creator>Logan Jenkins</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:43:12 +0000</pubDate>
      <link>https://dev.to/logan_works/a-small-react-pattern-that-removed-half-our-prop-drilling-3499</link>
      <guid>https://dev.to/logan_works/a-small-react-pattern-that-removed-half-our-prop-drilling-3499</guid>
      <description>&lt;p&gt;We had a settings page where props were threaded through four levels of components. Every new field touched five files.&lt;/p&gt;

&lt;p&gt;The fix wasn't a state library. It was composition:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;SettingsSection&lt;/span&gt; &lt;span class="na"&gt;title&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Notifications"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;NotificationFields&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;SettingsSection&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Instead of passing &lt;code&gt;value&lt;/code&gt; and &lt;code&gt;onChange&lt;/code&gt; down, each section owns its slice of state, and the page composes sections. The props stayed where they were used.&lt;/p&gt;

&lt;p&gt;We deleted about 200 lines of plumbing. The page is easier to read and the components are testable in isolation.&lt;/p&gt;

&lt;p&gt;I'm learning Kotlin Multiplatform next — mostly curiosity about sharing UI logic without sharing UI. If you've tried it, I'd love to compare notes.&lt;/p&gt;

</description>
      <category>react</category>
      <category>typescript</category>
      <category>frontend</category>
    </item>
  </channel>
</rss>
