<?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: Hossein Najafi</title>
    <description>The latest articles on DEV Community by Hossein Najafi (@hossein_najafi81).</description>
    <link>https://dev.to/hossein_najafi81</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%2F2537636%2Ff3d08162-5467-4d1c-9af4-9a39636492f1.jpg</url>
      <title>DEV Community: Hossein Najafi</title>
      <link>https://dev.to/hossein_najafi81</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hossein_najafi81"/>
    <language>en</language>
    <item>
      <title>I Finally Published My First NPM Package! 🎉</title>
      <dc:creator>Hossein Najafi</dc:creator>
      <pubDate>Sat, 12 Sep 2026 16:20:34 +0000</pubDate>
      <link>https://dev.to/hossein_najafi81/i-finally-published-my-first-npm-package-30om</link>
      <guid>https://dev.to/hossein_najafi81/i-finally-published-my-first-npm-package-30om</guid>
      <description>&lt;p&gt;Hello everyone 👋&lt;/p&gt;

&lt;p&gt;I’m really happy to finally share my first NPM package: taglite 🚀&lt;/p&gt;

&lt;p&gt;This package started from a simple need in one of my projects.&lt;/p&gt;

&lt;p&gt;I needed a Tag Input component, so I tried several different libraries. Each one had its own limitations. Some were missing features I needed, while others weren’t flexible enough to customize the way I wanted.&lt;/p&gt;

&lt;p&gt;So I decided to build my own.&lt;/p&gt;

&lt;p&gt;As I kept using it, I gradually added more features and improvements. Eventually, I thought, why not turn it into an independent package and share it with others?&lt;/p&gt;

&lt;p&gt;And that’s how taglite was born. 🚀&lt;/p&gt;

&lt;p&gt;What is taglite?&lt;/p&gt;

&lt;p&gt;taglite is a lightweight Tag Input component for React.&lt;/p&gt;

&lt;p&gt;My goal was to keep the API simple while still providing the features commonly needed in real-world projects.&lt;/p&gt;

&lt;p&gt;✨ Features&lt;/p&gt;

&lt;p&gt;🚀 Zero runtime dependencies&lt;br&gt;
🔷 Full TypeScript support&lt;br&gt;
⌨️ Add tags with Enter and define custom keys such as Tab&lt;br&gt;
📋 Copy &amp;amp; Paste support for creating multiple tags&lt;br&gt;
🧹 Normalize and Validate tags&lt;br&gt;
🚫 Prevent duplicate tags&lt;br&gt;
🔢 Limit the number of tags&lt;br&gt;
💬 Custom placeholder and hintText&lt;br&gt;
🔒 Read-only and Disabled modes&lt;br&gt;
🎨 Built-in themes such as Dark, Light, Dracula, and more&lt;br&gt;
🧩 Support for custom icons&lt;br&gt;
🔔 Callbacks for adding and removing tags&lt;br&gt;
⚙️ Support for Native HTML Input Attributes&lt;/p&gt;

&lt;p&gt;I’m also working on a new feature that allows you to customize the component’s color and appearance using a color passed through a prop. I’m planning to release it in the next few days. 🌈&lt;/p&gt;

&lt;p&gt;This was my first experience building and publishing an NPM package, and honestly, the process itself was one of the most interesting parts for me.&lt;/p&gt;

&lt;p&gt;From structuring the package and designing the API to testing, building, writing the documentation, and finally publishing it, there was a lot to learn.&lt;/p&gt;

&lt;p&gt;This is currently the first version, and I’m still working on improving it. I’ll probably add more features in future versions based on new needs and feedback.&lt;/p&gt;

&lt;p&gt;I’d really appreciate it if you gave it a try and shared your feedback. ❤️&lt;/p&gt;

&lt;p&gt;NPM: &lt;a href="https://www.npmjs.com/package/taglite" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/taglite&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/hossein-nj/taglite" rel="noopener noreferrer"&gt;https://github.com/hossein-nj/taglite&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>react</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I stopped relying on UI libraries and started building my own reusable components</title>
      <dc:creator>Hossein Najafi</dc:creator>
      <pubDate>Sat, 04 Jul 2026 14:19:23 +0000</pubDate>
      <link>https://dev.to/hossein_najafi81/how-i-stopped-relying-on-ui-libraries-and-started-building-my-own-reusable-components-3bn3</link>
      <guid>https://dev.to/hossein_najafi81/how-i-stopped-relying-on-ui-libraries-and-started-building-my-own-reusable-components-3bn3</guid>
      <description>&lt;p&gt;When I started working with React, I used UI libraries for almost everything — buttons, inputs, modals, you name it.&lt;/p&gt;

&lt;p&gt;It felt fast at first ⚡ I could build interfaces quickly without thinking too much about structure or design.&lt;/p&gt;

&lt;p&gt;But over time, I started noticing some problems:&lt;/p&gt;

&lt;p&gt;My projects became dependent on external libraries 📦&lt;br&gt;
Customizing components was often painful 😵‍💫&lt;br&gt;
I had less control over performance and design consistency 🎯&lt;br&gt;
I wasn’t really improving my component design skills 📉&lt;/p&gt;

&lt;p&gt;So I decided to change my approach.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;🧱 Building my own component system&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Instead of installing a new library every time, I started building my own reusable components from scratch:&lt;/p&gt;

&lt;p&gt;Button&lt;br&gt;
Input (with variants like password toggle, number formatting, etc.)&lt;br&gt;
Modal&lt;br&gt;
Form components&lt;/p&gt;

&lt;p&gt;At first, it took more time ⏳ But very quickly I noticed something important:&lt;/p&gt;

&lt;p&gt;I started understanding UI architecture much deeper than before 🧠&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;⚡ What I learned&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Reusability is not just about code ♻️&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It’s about designing components that can adapt to different use cases without rewriting logic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Props are powerful if used correctly 🎛️&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A well-designed props system can replace entire libraries in small to medium projects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Less dependency = more control 🧩&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I don’t have to wait for library updates or fight with overrides anymore.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;🚀 The result&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Now my projects are:&lt;/p&gt;

&lt;p&gt;More consistent in design 🎨&lt;br&gt;
Easier to maintain 🛠️&lt;br&gt;
More lightweight ⚡&lt;br&gt;
Fully under my control 🔒&lt;/p&gt;

&lt;p&gt;And most importantly, I feel like I actually understand what I’m building.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;💬 Final thought&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;UI libraries are great — but they shouldn’t replace understanding.&lt;/p&gt;

&lt;p&gt;Building your own components, even if simple, can completely change how you think as a frontend developer 💡&lt;/p&gt;

&lt;p&gt;If you’re a React developer, I highly recommend trying it at least once.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>react</category>
      <category>frontend</category>
    </item>
  </channel>
</rss>
