<?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: navid rezadoost</title>
    <description>The latest articles on DEV Community by navid rezadoost (@navid_rezadoost_33d170b80).</description>
    <link>https://dev.to/navid_rezadoost_33d170b80</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%2F3603061%2F7e8d9e87-b34a-48e2-b671-d2e7f58acbf3.jpg</url>
      <title>DEV Community: navid rezadoost</title>
      <link>https://dev.to/navid_rezadoost_33d170b80</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/navid_rezadoost_33d170b80"/>
    <language>en</language>
    <item>
      <title>Building custom socks5 for VsCode and other development tools</title>
      <dc:creator>navid rezadoost</dc:creator>
      <pubDate>Wed, 19 Nov 2025 12:02:05 +0000</pubDate>
      <link>https://dev.to/navid_rezadoost_33d170b80/building-custom-socks5-for-vscode-and-other-development-tools-50ib</link>
      <guid>https://dev.to/navid_rezadoost_33d170b80/building-custom-socks5-for-vscode-and-other-development-tools-50ib</guid>
      <description>&lt;h1&gt;
  
  
  Only VSCode Uses the VPN — The Rest of Your Computer Stays Chill
&lt;/h1&gt;

&lt;p&gt;How I stopped turning my whole laptop into a VPN zombie just to install a single extension&lt;/p&gt;

&lt;p&gt;If you're reading this, you probably know the pain.&lt;/p&gt;

&lt;p&gt;You're in a country (or a corporate network) where half the internet is blocked.&lt;br&gt;&lt;br&gt;
GitHub? Blocked.&lt;br&gt;&lt;br&gt;
VSCode Marketplace? Nope.&lt;br&gt;&lt;br&gt;
NPM/PyPI? Good luck.&lt;/p&gt;
&lt;h3&gt;
  
  
  So you fire up your VPN… and suddenly:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Your colleagues can't reach &lt;code&gt;localhost:3000&lt;/code&gt; anymore&lt;/li&gt;
&lt;li&gt;Your Android emulator thinks you're in the US&lt;/li&gt;
&lt;li&gt;Your banking app freaks out&lt;/li&gt;
&lt;li&gt;Your 300 Mbps connection turns into a potato&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Been there. Done that. Hated it.&lt;/p&gt;

&lt;p&gt;So I built something better: a tiny set of scripts that puts &lt;strong&gt;only VSCode (and whatever else you want)&lt;/strong&gt; behind the VPN, while everything else keeps your real IP and full local network access.&lt;/p&gt;

&lt;p&gt;Meet → &lt;strong&gt;[&lt;a href="https://github.com/navidrezadoost/dev-socks-isolation" rel="noopener noreferrer"&gt;https://github.com/navidrezadoost/dev-socks-isolation&lt;/a&gt;)&lt;/strong&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  &lt;strong&gt;The dream setup&lt;/strong&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Browser       → real IP ✓&lt;/li&gt;
&lt;li&gt;Discord       → real IP ✓&lt;/li&gt;
&lt;li&gt;Local dev server → accessible to teammates ✓&lt;/li&gt;
&lt;li&gt;Docker        → real IP ✓&lt;/li&gt;
&lt;li&gt;Banking app   → doesn't hate you ✓&lt;/li&gt;
&lt;li&gt;VSCode        → happily downloading extensions through VPN ✓&lt;/li&gt;
&lt;li&gt;Git clone     → works ✓&lt;/li&gt;
&lt;li&gt;NPM install   → no more "network timeout" ✓&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
  
  
  &lt;strong&gt;How does it actually work?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;On Linux (the hero platform):&lt;br&gt;&lt;br&gt;
We create a completely separate &lt;strong&gt;network namespace&lt;/strong&gt;, spin up OpenVPN + a SOCKS5 proxy (Dante) inside it, then punch a tiny hole so your host can talk to that proxy.&lt;/p&gt;

&lt;p&gt;Result? True isolation. Zero leaks. Your host doesn't even know a VPN exists.&lt;/p&gt;

&lt;p&gt;On Windows: Same thing, but inside WSL2 (yes, it works perfectly).&lt;br&gt;&lt;br&gt;
On macOS: We do the best we can with routing + SOCKS (no real namespaces, sorry Apple).&lt;/p&gt;
&lt;h3&gt;
  
  
  30-second test drive (Linux)
&lt;/h3&gt;


&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/navidrezadoost/dev-socks-isolation.git
&lt;span class="nb"&gt;cd &lt;/span&gt;vscode-socks5-vpn-namespace/linux/Ubuntu    &lt;span class="c"&gt;# or your distro&lt;/span&gt;
./connect.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;&lt;strong&gt;It will:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Detect your interface &amp;amp; IP automatically&lt;br&gt;
Ask for your .ovpn file (absolute path!)&lt;br&gt;
Offer to install missing packages&lt;br&gt;
Connect the VPN in an isolated namespace&lt;br&gt;
Start a SOCKS5 proxy&lt;br&gt;
Forward it to your host&lt;br&gt;
Optionally launch VSCode with the proxy&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;When it's done you get something like:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;Proxy address: socks5://10.200.200.2:1081
Your public IP through proxy: 185.102.34.567  ← VPN IP
Your real public IP: 89.42.123.456           ← unchanged
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Just launch VSCode like this forever:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;code &lt;span class="nt"&gt;--proxy-server&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"socks5://10.200.200.2:1081"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or make it permanent with a tiny desktop shortcut/alias.&lt;br&gt;
Want git and terminal tools too?&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git config &lt;span class="nt"&gt;--global&lt;/span&gt; http.proxy socks5://10.200.200.2:1081
curl &lt;span class="nt"&gt;--socks5-hostname&lt;/span&gt; 10.200.200.2:1081 https://ipinfo.io
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Real-life use cases (why people actually love this)&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Iran, Turkey, Russia, corporate offices → Access dev resources without breaking local stuff&lt;/li&gt;
&lt;li&gt;Pentesters on Kali/Parrot → Keep your recon traffic on one VPN and your IDE on another&lt;/li&gt;
&lt;li&gt;Privacy nerds → Only route work traffic through VPN, keep personal stuff direct&lt;/li&gt;
&lt;li&gt;Multiple VPNs at once → Run three namespaces with three different providers. No conflicts.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Current status&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Linux: Rock solid on 15+ distros (Ubuntu, Arch, Fedora, Kali, etc.)&lt;/li&gt;
&lt;li&gt;Windows (via WSL2): Full isolation, works great&lt;/li&gt;
&lt;li&gt;macOS: Works, but limited (no real namespaces)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All the ugly distro-specific package names and quirks are handled for you.&lt;br&gt;
Try it, seriously&lt;br&gt;
If you've ever screamed at your computer because you just wanted to install one VSCode extension without disconnecting from your local dev server… this is for you.&lt;br&gt;
→ &lt;a href="https://github.com/navidrezadoost/dev-socks-isolation/tree/main" rel="noopener noreferrer"&gt;https://github.com/navidrezadoost/dev-socks-isolation/tree/main&lt;/a&gt;&lt;br&gt;
Star it if it saves your sanity. PRs welcome (especially more distro support!).&lt;br&gt;
And yes — this whole thing was built because I got tired of choosing between "can code" and "can demo my code to colleagues" every single day.&lt;br&gt;
You're welcome&lt;br&gt;
P.S. To everyone still copy-pasting export http_proxy=socks5://127.0.0.1:1080 into every terminal tab in 2025… come to the light&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This version is perfect for dev.to (casual, relatable, meme-friendly) and also works great on Medium. It focuses on the problem, the emotions, and the "aha!" moment — exactly what readers love.&lt;br&gt;
Go post it and watch the stars roll in&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>networking</category>
      <category>vscode</category>
      <category>tooling</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The Last SVG Tool You’ll Ever Need: A Zero-Dependency Alternative to SVGR</title>
      <dc:creator>navid rezadoost</dc:creator>
      <pubDate>Sun, 09 Nov 2025 09:44:11 +0000</pubDate>
      <link>https://dev.to/navid_rezadoost_33d170b80/the-last-svg-tool-youll-ever-need-a-zero-dependency-alternative-to-svgr-10nc</link>
      <guid>https://dev.to/navid_rezadoost_33d170b80/the-last-svg-tool-youll-ever-need-a-zero-dependency-alternative-to-svgr-10nc</guid>
      <description>&lt;h1&gt;
  
  
  The Last SVG Tool You’ll Ever Need: SVGER-CLI 4.1, a Zero-Dependency Core, and Nine Framework Targets
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;Updated October 2026 — A closer look at unified SVG generation, build integrations, security, and reproducible workflows.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #react #vue #svelte #opensource&lt;/p&gt;

&lt;h2&gt;
  
  
  The SVG Problem Hasn't Disappeared. It's Just Become More Complicated.
&lt;/h2&gt;

&lt;p&gt;Imagine working on a frontend platform with multiple applications.&lt;/p&gt;

&lt;p&gt;One application uses React. Another uses Vue. Your design system needs to support Angular. A newer project uses Svelte, while a mobile application uses React Native.&lt;/p&gt;

&lt;p&gt;All of them need the same icons.&lt;/p&gt;

&lt;p&gt;The SVG source files are identical, but the surrounding development workflows are not.&lt;/p&gt;

&lt;p&gt;For React, you might use SVGR. For Vue, perhaps a Vite SVG loader. Svelte, Angular, and React Native introduce their own component formats, runtime requirements, and conventions.&lt;/p&gt;

&lt;p&gt;Each solution can work well independently. The difficulty appears when you're responsible for &lt;strong&gt;maintaining a consistent SVG pipeline across multiple frameworks&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;You start asking questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How do we enforce consistent component naming?&lt;/li&gt;
&lt;li&gt;How do we regenerate icons without accidentally overwriting unrelated files?&lt;/li&gt;
&lt;li&gt;Can we detect stale generated components in CI?&lt;/li&gt;
&lt;li&gt;How should we handle malformed or potentially unsafe SVG input?&lt;/li&gt;
&lt;li&gt;Can the same SVG catalog support multiple frameworks?&lt;/li&gt;
&lt;li&gt;Can we automate regeneration without maintaining a separate workflow for every application?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;At this point, SVG conversion stops being a simple file transformation.&lt;/p&gt;

&lt;p&gt;It becomes an engineering workflow.&lt;/p&gt;

&lt;p&gt;That's the problem &lt;a href="https://github.com/faezemohades/svger-cli" rel="noopener noreferrer"&gt;SVGER-CLI&lt;/a&gt; aims to solve.&lt;/p&gt;




&lt;h2&gt;
  
  
  Introducing SVGER-CLI
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;SVGER-CLI is an open-source SVG-to-component generation tool with a dependency-light core, nine framework targets, and integrations for common JavaScript build systems.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The project is designed around a straightforward principle:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Keep the SVG processing workflow consistent, while allowing each frontend framework to receive code in its own native component format.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Instead of configuring a completely separate conversion tool for every framework, you use a common CLI and select the desired output target.&lt;/p&gt;

&lt;p&gt;SVGER-CLI supports:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Framework target&lt;/th&gt;
&lt;th&gt;Typical generated format&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;React&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.tsx&lt;/code&gt; / &lt;code&gt;.jsx&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;React Native&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.tsx&lt;/code&gt; / &lt;code&gt;.jsx&lt;/code&gt; using native SVG primitives&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vue 3&lt;/td&gt;
&lt;td&gt;&lt;code&gt;.vue&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Angular&lt;/td&gt;
&lt;td&gt;&lt;code&gt;.component.ts&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Svelte&lt;/td&gt;
&lt;td&gt;&lt;code&gt;.svelte&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Solid&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.tsx&lt;/code&gt; / &lt;code&gt;.jsx&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Preact&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.tsx&lt;/code&gt; / &lt;code&gt;.jsx&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lit&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.ts&lt;/code&gt; / &lt;code&gt;.js&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vanilla JavaScript/TypeScript&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;.js&lt;/code&gt; / &lt;code&gt;.ts&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are nine generation targets, not nine bundled frontend frameworks.&lt;/p&gt;

&lt;p&gt;SVGER-CLI generates source code. Your application still provides the appropriate framework runtime, compiler, and build configuration.&lt;/p&gt;

&lt;p&gt;For example, React Native consumers need a compatible SVG renderer such as &lt;code&gt;react-native-svg&lt;/code&gt;, and Angular output requires TypeScript.&lt;/p&gt;

&lt;p&gt;That distinction matters, especially in projects that maintain several component libraries from one shared asset catalog.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Does "Zero Dependency" Actually Mean?
&lt;/h2&gt;

&lt;p&gt;Let's clarify an important point.&lt;/p&gt;

&lt;p&gt;SVGER-CLI's ordinary SVG-to-component generation path is designed without required third-party runtime dependencies for its core processing.&lt;/p&gt;

&lt;p&gt;This is not the same as claiming that installing the package can never install another package.&lt;/p&gt;

&lt;p&gt;The project has development dependencies for building and testing itself, and it declares optional packages for functionality such as image comparison.&lt;/p&gt;

&lt;p&gt;For example, optional visual comparison uses packages including &lt;code&gt;pixelmatch&lt;/code&gt;, &lt;code&gt;pngjs&lt;/code&gt;, and a separately installed compatible version of &lt;code&gt;sharp&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;So the accurate statement is:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SVGER-CLI provides core SVG generation without required runtime dependencies, while keeping specialized functionality optional.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Why does that matter?&lt;/p&gt;

&lt;p&gt;A smaller mandatory dependency surface can simplify installation, auditing, maintenance, and dependency management. But dependency count alone does not prove that a tool is faster or more secure.&lt;/p&gt;

&lt;p&gt;Actual performance and security depend on implementation, input characteristics, runtime conditions, and testing.&lt;/p&gt;

&lt;p&gt;The architecture is the advantage. The performance still needs to be measured.&lt;/p&gt;




&lt;h2&gt;
  
  
  Getting Started in 60 Seconds
&lt;/h2&gt;

&lt;p&gt;SVGER-CLI's package declares support for Node.js &lt;code&gt;&amp;gt;=18.17.0&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That is a compatibility floor, not a recommendation to run an end-of-life Node.js version in production. For new projects, use a maintained Node.js LTS release supported by your environment.&lt;/p&gt;

&lt;p&gt;Install the version used throughout this article:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--save-dev&lt;/span&gt; svger-cli@4.1.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Confirm the installed CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx &lt;span class="nt"&gt;--no-install&lt;/span&gt; svger-cli &lt;span class="nt"&gt;--version&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Inspect available commands:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx &lt;span class="nt"&gt;--no-install&lt;/span&gt; svger-cli &lt;span class="nt"&gt;--help&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now suppose your project contains:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;my-project/
├── assets/
│   └── icons/
│       ├── home.svg
│       ├── search.svg
│       └── settings.svg
├── src/
│   └── components/
└── package.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Generate React TypeScript components:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx svger-cli build &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons &lt;span class="se"&gt;\&lt;/span&gt;
  ./src/components/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;SVGER-CLI reads the SVG files and generates framework-specific components in the destination directory.&lt;/p&gt;

&lt;p&gt;The exact filenames, exported symbols, and generated index files depend on your naming and output configuration.&lt;/p&gt;

&lt;p&gt;For a single file, use &lt;code&gt;generate&lt;/code&gt; instead:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx svger-cli generate &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons/home.svg &lt;span class="se"&gt;\&lt;/span&gt;
  ./src/components/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's the basic workflow: source SVG, selected framework, generated component.&lt;/p&gt;

&lt;p&gt;But there is considerably more to the project than conversion.&lt;/p&gt;




&lt;h2&gt;
  
  
  One SVG Catalog, Nine Framework Targets
&lt;/h2&gt;

&lt;p&gt;The real benefit appears when several frontend applications share the same icon library.&lt;/p&gt;

&lt;p&gt;You can generate different implementations from the same SVG directory.&lt;/p&gt;

&lt;h3&gt;
  
  
  React
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Vue 3
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/vue &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; vue &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--composition&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;--composition&lt;/code&gt; option requests Vue's Composition API / &lt;code&gt;&amp;lt;script setup&amp;gt;&lt;/code&gt; style.&lt;/p&gt;

&lt;h3&gt;
  
  
  Angular
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/angular &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; angular &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--standalone&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Angular generates TypeScript components. JavaScript output is intentionally unsupported for this target.&lt;/p&gt;

&lt;h3&gt;
  
  
  Svelte
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/svelte &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; svelte &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  React Native
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/native &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react-native &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;React Native components target native SVG primitives rather than browser SVG elements.&lt;/p&gt;

&lt;h3&gt;
  
  
  Solid
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/solid &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; solid &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Preact
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/preact &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; preact &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Lit
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/lit &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; lit &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Vanilla JavaScript
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/vanilla &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; vanilla &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--no-typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now a monorepo can keep shared SVG source files in one place while generating components for several applications:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;design-system/
├── assets/
│   └── icons/
│       ├── home.svg
│       ├── search.svg
│       └── settings.svg
│
├── packages/
│   ├── icons-react/
│   ├── icons-vue/
│   ├── icons-angular/
│   └── icons-svelte/
│
└── package.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each package can have its own generation command, output folder, compilation checks, and release lifecycle.&lt;/p&gt;

&lt;p&gt;The source of the icons remains consistent.&lt;/p&gt;

&lt;p&gt;The generated implementation belongs to the target framework.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; Use separate output directories for different targets. Do not mix manually maintained components and generator-owned files in the same directory.&lt;/p&gt;




&lt;h2&gt;
  
  
  Beyond Conversion: What Makes SVGER-CLI Different?
&lt;/h2&gt;

&lt;p&gt;SVG conversion is useful. Managing the resulting artifacts reliably is where a tool becomes more valuable in larger projects.&lt;/p&gt;

&lt;p&gt;SVGER-CLI includes several capabilities aimed at that second problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Preview a Build Without Writing Files
&lt;/h3&gt;

&lt;p&gt;Before regenerating hundreds of components, you may want to know what the command intends to do.&lt;/p&gt;

&lt;p&gt;SVGER-CLI provides a dry-run mode:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--dry-run&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For automation, request a structured report:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--dry-run&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--format&lt;/span&gt; json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is particularly useful when introducing a generator into an existing repository.&lt;/p&gt;

&lt;p&gt;You can review the proposed work before committing changes.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Detect Stale Generated Components in CI
&lt;/h3&gt;

&lt;p&gt;Generated components can drift from their SVG sources.&lt;/p&gt;

&lt;p&gt;Someone changes an icon but forgets to regenerate the corresponding component. Another developer changes generator configuration without rebuilding the output.&lt;/p&gt;

&lt;p&gt;SVGER-CLI includes a check mode:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--check&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The command fails when the generated artifacts do not match the expected output.&lt;/p&gt;

&lt;p&gt;That makes it suitable for CI pipelines where generated files are committed to version control.&lt;/p&gt;

&lt;p&gt;You can also inspect differences without writing:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--diff&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The distinction is simple:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Mode&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Normal build&lt;/td&gt;
&lt;td&gt;Generate and write output&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;--dry-run&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Plan generation without committing files&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;--check&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Detect outdated output&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;--diff&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Report differences without writing&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are mutually exclusive build modes.&lt;/p&gt;

&lt;p&gt;For engineering teams, this is more valuable than simply making component generation faster.&lt;/p&gt;

&lt;p&gt;It makes generated code easier to verify.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Detect Naming Collisions Before Writing
&lt;/h3&gt;

&lt;p&gt;Consider these SVG filenames:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;home-icon.svg
HomeIcon.svg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Depending on your naming rules, both might resolve to the same component name.&lt;/p&gt;

&lt;p&gt;Without collision detection, a generator could accidentally overwrite one component with another.&lt;/p&gt;

&lt;p&gt;SVGER-CLI supports collision policies and defaults to rejecting ambiguous output collisions.&lt;/p&gt;

&lt;p&gt;You can make that explicit:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--collision&lt;/span&gt; error
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Alternative policies exist for cases where choosing a winner is intentional, but a strict error is a sensible default for shared design systems.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Recover From Interrupted Generation
&lt;/h3&gt;

&lt;p&gt;A large generation operation can be interrupted.&lt;/p&gt;

&lt;p&gt;A process crashes. A machine loses power. A filesystem operation fails partway through applying output changes.&lt;/p&gt;

&lt;p&gt;SVGER-CLI includes transaction-oriented output handling and a recovery command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger recover ./generated/react &lt;span class="nt"&gt;--format&lt;/span&gt; json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The recovery system is designed to use transaction journals and controlled rollback behavior rather than treating an interrupted build as an arbitrary filesystem state.&lt;/p&gt;

&lt;p&gt;This does not mean every interruption is automatically recoverable under every operating system or failure condition.&lt;/p&gt;

&lt;p&gt;Recovery relies on filesystem trust and permission assumptions, and platform-specific behavior should be validated before relying on it in production workflows.&lt;/p&gt;

&lt;p&gt;Still, the underlying idea is important:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Output generation should consider failure recovery, not just successful execution.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Protect Selected Files
&lt;/h3&gt;

&lt;p&gt;Sometimes an asset should not be changed through the normal managed workflow.&lt;/p&gt;

&lt;p&gt;For example, a brand logo may require explicit review before modifications are allowed.&lt;/p&gt;

&lt;p&gt;SVGER-CLI provides file-lock commands:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger lock ./assets/icons/company-logo.svg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And later:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger unlock ./assets/icons/company-logo.svg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These are managed workflow protections, not operating-system security locks.&lt;/p&gt;

&lt;p&gt;They help teams express intent around assets that require special handling.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Watch Mode for Local Development
&lt;/h3&gt;

&lt;p&gt;During active development, you may want components to regenerate as SVG files change.&lt;/p&gt;

&lt;p&gt;Use the dedicated watch command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger watch ./assets/icons ./generated/react
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Watch mode observes source changes and triggers regeneration.&lt;/p&gt;

&lt;p&gt;Framework and language preferences for watch workflows should be placed in the project configuration. Do not assume that every &lt;code&gt;build&lt;/code&gt; flag is accepted by the &lt;code&gt;watch&lt;/code&gt; command.&lt;/p&gt;




&lt;h2&gt;
  
  
  Security: SVG Files Are Not Always Harmless
&lt;/h2&gt;

&lt;p&gt;An SVG is not merely a collection of vector paths.&lt;/p&gt;

&lt;p&gt;It is an XML-based document format that can contain external resource references, styles, embedded content, and constructs that may be inappropriate for a source-code generation pipeline.&lt;/p&gt;

&lt;p&gt;For an individual developer converting known assets, this may rarely become visible.&lt;/p&gt;

&lt;p&gt;For a team processing files from designers, external packages, uploads, or third-party sources, the input boundary becomes more important.&lt;/p&gt;

&lt;p&gt;SVGER-CLI's security model includes a bounded XML scanner before normal optimization and artifact generation.&lt;/p&gt;

&lt;p&gt;By default, its unsafe-input policy is &lt;code&gt;reject&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The validator rejects classes of input such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Malformed or unsupported XML structures.&lt;/li&gt;
&lt;li&gt;DTD and entity declarations.&lt;/li&gt;
&lt;li&gt;Event-handler attributes and active embedded elements.&lt;/li&gt;
&lt;li&gt;Prohibited external resource references.&lt;/li&gt;
&lt;li&gt;Disallowed CSS resource-loading constructs.&lt;/li&gt;
&lt;li&gt;Inputs exceeding configured resource limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The scanner also enforces limits on document size, nesting, and structural complexity.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--unsafe-input-policy&lt;/span&gt; reject &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--max-input-size&lt;/span&gt; 10485760
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The example sets a maximum input size of 10 MiB.&lt;/p&gt;

&lt;p&gt;There is also an explicit &lt;code&gt;strip&lt;/code&gt; mode for selected unsafe constructs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--unsafe-input-policy&lt;/span&gt; strip
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;However, &lt;strong&gt;strip mode is not a general-purpose SVG sanitizer&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It can remove content, change appearance, or reject unsupported XML altogether. It should not be used simply to bypass a security diagnostic.&lt;/p&gt;

&lt;p&gt;Nor should the input scanner be described as a complete security certification for every SVG feature, browser, or rendering environment.&lt;/p&gt;

&lt;p&gt;The useful guarantee is narrower: the generator applies a documented admission policy to the SVG subset it accepts.&lt;/p&gt;

&lt;p&gt;For production systems, that's a much more meaningful engineering claim than simply saying that SVG inputs are safe.&lt;/p&gt;




&lt;h2&gt;
  
  
  Build Tool Integration: Beyond the CLI
&lt;/h2&gt;

&lt;p&gt;One of the biggest improvements in the SVGER-CLI ecosystem is its integration surface.&lt;/p&gt;

&lt;p&gt;The package provides dedicated entry points for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Webpack&lt;/li&gt;
&lt;li&gt;Vite&lt;/li&gt;
&lt;li&gt;Rollup&lt;/li&gt;
&lt;li&gt;Babel&lt;/li&gt;
&lt;li&gt;Next.js&lt;/li&gt;
&lt;li&gt;Jest&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These integrations let teams move SVG generation into existing development and build workflows instead of maintaining separate manual commands.&lt;/p&gt;

&lt;h3&gt;
  
  
  Example: Vite + React
&lt;/h3&gt;

&lt;p&gt;Install SVGER-CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--save-dev&lt;/span&gt; svger-cli@4.1.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Configure &lt;code&gt;vite.config.mjs&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;defineConfig&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;vite&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;svgerVitePlugin&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/vite&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nf"&gt;defineConfig&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;plugins&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="nf"&gt;svgerVitePlugin&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
      &lt;span class="na"&gt;source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;./assets/icons&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;output&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;./src/generated/icons&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;framework&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;typescript&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;hmr&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="na"&gt;generateIndex&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}),&lt;/span&gt;
  &lt;span class="p"&gt;],&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now SVG component generation is part of the Vite-oriented workflow.&lt;/p&gt;

&lt;p&gt;With index generation enabled, consumers may import from a generated barrel rather than referencing every component file individually.&lt;/p&gt;

&lt;p&gt;Always inspect the actual exported names, since they depend on component naming and output configuration.&lt;/p&gt;

&lt;h3&gt;
  
  
  Other Integration Entry Points
&lt;/h3&gt;

&lt;p&gt;The library provides explicit ESM package subpaths:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;SvgerWebpackPlugin&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/webpack&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;svgerVitePlugin&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/vite&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;svgerRollupPlugin&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/rollup&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;svgerBabelPlugin&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/babel&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;withSvger&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;svger-cli/nextjs&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Jest-related entry points are available for SVG transformations and test mocks.&lt;/p&gt;

&lt;p&gt;SVGER-CLI is published as an ES module package, so use its documented ESM integrations unless your particular toolchain has been tested with another loading arrangement.&lt;/p&gt;

&lt;p&gt;For detailed configuration examples, see the &lt;a href="https://github.com/faezemohades/svger-cli/blob/main/docs/INTEGRATIONS.md" rel="noopener noreferrer"&gt;integration documentation&lt;/a&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Configuration Without Repeating Every Option
&lt;/h2&gt;

&lt;p&gt;Commands are useful for experimentation.&lt;/p&gt;

&lt;p&gt;For a maintained project, configuration should be versioned alongside the source code.&lt;/p&gt;

&lt;p&gt;SVGER-CLI uses &lt;code&gt;.svgconfig.json&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Create one with:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger config &lt;span class="nt"&gt;--init&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A possible React configuration is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"./assets/icons"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"output"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"./src/generated/icons"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"framework"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"react"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"typescript"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"defaultWidth"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;24&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"defaultHeight"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;24&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"defaultFill"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"currentColor"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"unsafeInputPolicy"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"reject"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"maxInputSizeBytes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;10485760&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"outputConfig"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"naming"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"pascal"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This keeps important generation decisions visible in source control.&lt;/p&gt;

&lt;p&gt;You can inspect the saved configuration:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger config &lt;span class="nt"&gt;--show&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or explain resolved values and their sources:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger config &lt;span class="nt"&gt;--explain&lt;/span&gt; framework &lt;span class="nt"&gt;--format&lt;/span&gt; json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;SVGER-CLI resolves configuration using built-in defaults, project configuration, compiler options, and explicit build overrides.&lt;/p&gt;

&lt;p&gt;For teams operating several applications, this makes configuration behavior easier to inspect and debug.&lt;/p&gt;




&lt;h2&gt;
  
  
  Optimization and Visual Correctness
&lt;/h2&gt;

&lt;p&gt;SVG optimization deserves its own discussion.&lt;/p&gt;

&lt;p&gt;Reducing source size is useful, but removing or rewriting SVG data can affect rendering.&lt;/p&gt;

&lt;p&gt;An optimizer might change attributes, path representations, numeric precision, or structural details. Some changes are harmless; others depend on how the SVG is used.&lt;/p&gt;

&lt;p&gt;SVGER-CLI provides standalone optimization:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger optimize &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons/home.svg &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/optimized/home.svg &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--level&lt;/span&gt; balanced
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Component generation also supports optimization levels:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger build ./assets/icons ./generated/react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--optimize&lt;/span&gt; basic
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Supported build optimization levels include &lt;code&gt;none&lt;/code&gt;, &lt;code&gt;basic&lt;/code&gt;, &lt;code&gt;balanced&lt;/code&gt;, &lt;code&gt;aggressive&lt;/code&gt;, and &lt;code&gt;maximum&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;These are configuration levels, not promises of a particular percentage reduction or guaranteed pixel-equivalent output.&lt;/p&gt;

&lt;p&gt;It's important to validate optimized assets in the actual application.&lt;/p&gt;

&lt;h3&gt;
  
  
  Optional Visual Comparison
&lt;/h3&gt;

&lt;p&gt;SVGER-CLI also has an optional raster-based comparison path.&lt;/p&gt;

&lt;p&gt;It requires additional packages and a compatible Node.js runtime. In the v4.1 documentation, visual rasterization requires Node.js &lt;code&gt;&amp;gt;=20.9.0&lt;/code&gt; and &lt;code&gt;sharp &amp;gt;=0.35.5&lt;/code&gt;, with &lt;code&gt;pixelmatch&lt;/code&gt; and &lt;code&gt;pngjs&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;For a project using a compatible runtime:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--save-dev&lt;/span&gt; sharp@^0.35.5 pixelmatch pngjs
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Visual validation can be requested through the documented optimizer path:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;svger optimize &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons/home.svg &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/optimized/home.svg &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--level&lt;/span&gt; balanced &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--validate&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Visual comparison is a supplementary check. It is not a proof that all SVG semantics, accessibility behavior, or browser rendering characteristics are identical.&lt;/p&gt;

&lt;p&gt;That distinction is especially relevant for sophisticated icons that use masks, filters, gradients, CSS, or other rendering features.&lt;/p&gt;




&lt;h2&gt;
  
  
  What About Performance?
&lt;/h2&gt;

&lt;p&gt;The original version of this article compared SVGER-CLI, SVGR, and other SVG tools using a small table of execution times.&lt;/p&gt;

&lt;p&gt;For an engineering tool, performance numbers should be reproducible rather than promotional.&lt;/p&gt;

&lt;p&gt;A fair comparison needs to control variables such as:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The exact version of each tool.&lt;/li&gt;
&lt;li&gt;The same SVG input corpus.&lt;/li&gt;
&lt;li&gt;Equivalent output requirements and optimization settings.&lt;/li&gt;
&lt;li&gt;Node.js and operating-system versions.&lt;/li&gt;
&lt;li&gt;Cold-start versus warm-process execution.&lt;/li&gt;
&lt;li&gt;Output correctness and framework compilation.&lt;/li&gt;
&lt;li&gt;Multiple benchmark iterations, reporting median and tail latency.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Install size, dependency count, and transformation speed are also separate measurements.&lt;/p&gt;

&lt;p&gt;A tool with no required core runtime dependencies is not automatically the fastest converter. Likewise, a faster conversion isn't very useful if its generated output does not compile or faithfully represent the input.&lt;/p&gt;

&lt;h3&gt;
  
  
  A More Reproducible Approach
&lt;/h3&gt;

&lt;p&gt;SVGER-CLI maintains a local evaluation workflow for comparing its production Svelte generation path with the opt-in experimental Svelte IR implementation.&lt;/p&gt;

&lt;p&gt;From a development checkout, maintainers can run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm run build

npm run evaluate:local &lt;span class="nt"&gt;--&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--groups&lt;/span&gt; 50,750 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--warmups&lt;/span&gt; 8 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--samples&lt;/span&gt; 40 &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--output&lt;/span&gt; ./evaluation.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The evaluator records information such as timing distributions, output digests, host metadata, and selected quality checks.&lt;/p&gt;

&lt;p&gt;It is not an SVGR-versus-SVGER benchmark, and it should not be presented as one.&lt;/p&gt;

&lt;p&gt;That's a useful direction for the project: &lt;strong&gt;publish measurements that other developers can inspect and reproduce, including unfavorable results.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Rather than claiming a universal speed advantage, I recommend benchmarking SVGER-CLI on the real SVG catalog and frameworks used by your team.&lt;/p&gt;




&lt;h2&gt;
  
  
  Experimental Features Should Stay Explicit
&lt;/h2&gt;

&lt;p&gt;SVGER-CLI's default Svelte generation path uses its established legacy compiler.&lt;/p&gt;

&lt;p&gt;The v4.1 source also documents an opt-in Svelte IR compiler for a bounded subset of static SVG input.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"framework"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"svelte"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"typescript"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"svelteCompiler"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"ir-v1"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is an experimental compiler route rather than a replacement for the normal generation pipeline.&lt;/p&gt;

&lt;p&gt;Unsupported constructs are rejected, and the project does not promise complete SVG semantic, accessibility, or browser-rendering equivalence.&lt;/p&gt;

&lt;p&gt;The project's local evaluation has also shown cases where the opt-in IR compiler is slower than the legacy implementation.&lt;/p&gt;

&lt;p&gt;That is precisely why opt-in experimentation and measured qualification are preferable to silently changing the default compiler.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Practical CI Workflow
&lt;/h2&gt;

&lt;p&gt;Let's connect everything into a realistic engineering workflow.&lt;/p&gt;

&lt;p&gt;Suppose your React project stores icons in &lt;code&gt;assets/icons&lt;/code&gt; and commits generated components under &lt;code&gt;src/generated/icons&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;A typical local workflow is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Generate components&lt;/span&gt;
svger build ./assets/icons ./src/generated/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;

&lt;span class="c"&gt;# Review proposed changes without writing&lt;/span&gt;
svger build ./assets/icons ./src/generated/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--diff&lt;/span&gt;

&lt;span class="c"&gt;# Verify generated output is current&lt;/span&gt;
svger build ./assets/icons ./src/generated/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--check&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your CI pipeline can install dependencies from the committed lockfile:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm ci
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then run the same check command:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx svger-cli build ./assets/icons ./src/generated/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--check&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A nonzero result for stale artifacts can fail the CI job.&lt;/p&gt;

&lt;p&gt;You should also run your application's existing TypeScript checks, framework compiler, and tests.&lt;/p&gt;

&lt;p&gt;This establishes a useful engineering contract:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SVG sources and generation configuration determine expected artifacts, and CI verifies that the committed output remains synchronized.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For multi-framework repositories, create a separate check for each generated target.&lt;/p&gt;




&lt;h2&gt;
  
  
  When Should You Use SVGER-CLI Instead of SVGR?
&lt;/h2&gt;

&lt;p&gt;SVGR remains a useful choice for projects focused specifically on converting SVGs into React components.&lt;/p&gt;

&lt;p&gt;SVGER-CLI is especially interesting when your needs extend beyond that.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Requirement&lt;/th&gt;
&lt;th&gt;What SVGER-CLI offers&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Multiple frontend frameworks&lt;/td&gt;
&lt;td&gt;Nine generation targets under one CLI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;React-only component conversion&lt;/td&gt;
&lt;td&gt;Supported, with other tools also viable&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shared icon catalogs&lt;/td&gt;
&lt;td&gt;Per-framework output directories&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build pipeline integration&lt;/td&gt;
&lt;td&gt;Webpack, Vite, Rollup, Babel, Next.js, Jest&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reproducible generated artifacts&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;--check&lt;/code&gt;, &lt;code&gt;--diff&lt;/code&gt;, &lt;code&gt;--dry-run&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Input admission controls&lt;/td&gt;
&lt;td&gt;Default unsafe-SVG rejection and resource bounds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Interrupted output handling&lt;/td&gt;
&lt;td&gt;Transaction-oriented output and recovery commands&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Custom workflow behavior&lt;/td&gt;
&lt;td&gt;Configuration and plugin extension points&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Core dependency management&lt;/td&gt;
&lt;td&gt;No required third-party runtime dependencies for normal generation&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;SVGER-CLI is not intended to eliminate every other SVG library.&lt;/p&gt;

&lt;p&gt;It does not replace frontend runtimes, a complete browser rendering environment, general-purpose XML tooling, or every SVG transformation that may be available in specialized libraries.&lt;/p&gt;

&lt;p&gt;Its value is in &lt;strong&gt;unifying and controlling the workflow that turns SVG assets into framework components&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For a small React-only application, another tool might be sufficient.&lt;/p&gt;

&lt;p&gt;For a design system serving multiple applications, the broader workflow can be compelling.&lt;/p&gt;




&lt;h2&gt;
  
  
  A Few Limitations Worth Knowing
&lt;/h2&gt;

&lt;p&gt;No developer tool should be described as universally suitable without discussing its boundaries.&lt;/p&gt;

&lt;p&gt;Some important considerations for SVGER-CLI are:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Framework correctness:&lt;/strong&gt; Generated code must still be compiled and tested against the target framework and its supported version.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SVG coverage:&lt;/strong&gt; Security admission and compiler transformations operate on documented supported input. Not every valid SVG feature necessarily has equivalent behavior across every generated framework.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Platform recovery:&lt;/strong&gt; Transaction recovery has filesystem permission and trust assumptions. Validate sensitive recovery workflows on your actual target operating systems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TypeScript consumers:&lt;/strong&gt; Some public declarations may require Node.js type definitions, depending on which APIs your application imports and how its TypeScript environment is configured.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Optional visual comparison:&lt;/strong&gt; Rasterization requires extra packages and does not prove universal pixel or semantic equivalence.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Performance:&lt;/strong&gt; The project should be judged through reproducible workloads, not unqualified claims about being several times faster than competing tools.&lt;/p&gt;

&lt;p&gt;These limitations do not undermine the purpose of SVGER-CLI.&lt;/p&gt;

&lt;p&gt;They define where more testing, documentation, and engineering work add value.&lt;/p&gt;




&lt;h2&gt;
  
  
  Who Is SVGER-CLI For?
&lt;/h2&gt;

&lt;p&gt;I see particularly strong use cases in five environments.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Design systems:&lt;/strong&gt; Maintain a shared icon catalog and generate compatible components for multiple frontend applications.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Monorepos:&lt;/strong&gt; Keep framework-specific output packages synchronized with a single source asset directory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Microfrontend architectures:&lt;/strong&gt; Support teams working with React, Angular, Vue, and other frameworks without forcing identical component runtimes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Component libraries:&lt;/strong&gt; Generate and publish framework-specific icon packages with predictable naming, exports, and build checks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Engineering teams with CI requirements:&lt;/strong&gt; Detect stale artifacts, inspect diffs, apply input admission policies, and reduce manual regeneration mistakes.&lt;/p&gt;

&lt;p&gt;If you're managing one SVG file in one application, the CLI can be convenient.&lt;/p&gt;

&lt;p&gt;If you're managing hundreds of SVG files across multiple frameworks and contributors, the engineering workflow is where it becomes more interesting.&lt;/p&gt;




&lt;h2&gt;
  
  
  Try SVGER-CLI
&lt;/h2&gt;

&lt;p&gt;Get started with the v4.1.0 package:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--save-dev&lt;/span&gt; svger-cli@4.1.0
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Generate your first components:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx svger-cli build &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons &lt;span class="se"&gt;\&lt;/span&gt;
  ./src/generated/icons &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; react &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or choose a different framework:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx svger-cli build &lt;span class="se"&gt;\&lt;/span&gt;
  ./assets/icons &lt;span class="se"&gt;\&lt;/span&gt;
  ./src/generated/vue &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--framework&lt;/span&gt; vue &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--composition&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--typescript&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Explore the project:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/faezemohades/svger-cli" rel="noopener noreferrer"&gt;https://github.com/faezemohades/svger-cli&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;npm:&lt;/strong&gt; &lt;a href="https://www.npmjs.com/package/svger-cli" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/svger-cli&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Documentation:&lt;/strong&gt; &lt;a href="https://faezemohades.github.io/svger-cli/" rel="noopener noreferrer"&gt;https://faezemohades.github.io/svger-cli/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CLI reference:&lt;/strong&gt; &lt;a href="https://github.com/faezemohades/svger-cli/blob/main/docs/CLI-REFERENCE.md" rel="noopener noreferrer"&gt;https://github.com/faezemohades/svger-cli/blob/main/docs/CLI-REFERENCE.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Framework guide:&lt;/strong&gt; &lt;a href="https://github.com/faezemohades/svger-cli/blob/main/docs/FRAMEWORK-GUIDE.md" rel="noopener noreferrer"&gt;https://github.com/faezemohades/svger-cli/blob/main/docs/FRAMEWORK-GUIDE.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security policy:&lt;/strong&gt; &lt;a href="https://github.com/faezemohades/svger-cli/blob/main/SECURITY.md" rel="noopener noreferrer"&gt;https://github.com/faezemohades/svger-cli/blob/main/SECURITY.md&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Issues and feedback:&lt;/strong&gt; &lt;a href="https://github.com/faezemohades/svger-cli/issues" rel="noopener noreferrer"&gt;https://github.com/faezemohades/svger-cli/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project is open source under the MIT license. Contributions, reproducible bug reports, compatibility feedback, and real-world benchmark results are welcome.&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;SVG conversion is easy to underestimate.&lt;/p&gt;

&lt;p&gt;At first, the problem appears to be replacing an &lt;code&gt;&amp;lt;svg&amp;gt;&lt;/code&gt; tag with a React component.&lt;/p&gt;

&lt;p&gt;As a project grows, the real challenges are different: consistent generation, multiple framework targets, output naming, reproducibility, security boundaries, CI integration, and handling failures.&lt;/p&gt;

&lt;p&gt;SVGER-CLI approaches those problems as parts of one workflow.&lt;/p&gt;

&lt;p&gt;Its goal isn't simply to generate more component formats. It's to make SVG processing easier to maintain as engineering systems become more complex.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One SVG catalog. Nine framework targets. One consistent generation workflow.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That is the direction we're building toward with SVGER-CLI.&lt;/p&gt;

&lt;p&gt;If you're working on a design system, monorepo, or multi-framework frontend platform, give it a try and share what works—and what still needs improvement.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Happy building! 🚀&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I contribute to the SVGER-CLI project. This article describes its documented capabilities and known limitations rather than an independently verified performance comparison.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>vue</category>
      <category>angular</category>
      <category>svelte</category>
    </item>
  </channel>
</rss>
