<?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: Suhel</title>
    <description>The latest articles on DEV Community by Suhel (@suhel_withai_8db26993d99).</description>
    <link>https://dev.to/suhel_withai_8db26993d99</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3277089%2F0a9ed823-f12b-4feb-9002-38752dcd2136.png</url>
      <title>DEV Community: Suhel</title>
      <link>https://dev.to/suhel_withai_8db26993d99</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/suhel_withai_8db26993d99"/>
    <language>en</language>
    <item>
      <title>🔍 Your .env file shouldn’t be a mystery box.</title>
      <dc:creator>Suhel</dc:creator>
      <pubDate>Thu, 19 Jun 2025 14:48:58 +0000</pubDate>
      <link>https://dev.to/suhel_withai_8db26993d99/your-env-file-shouldnt-be-a-mystery-box-5ij</link>
      <guid>https://dev.to/suhel_withai_8db26993d99/your-env-file-shouldnt-be-a-mystery-box-5ij</guid>
      <description>&lt;p&gt;Over time, every project ends up with a cluttered, outdated, and hard-to-audit .env file.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Some variables are used.&lt;/li&gt;
&lt;li&gt;Some are not.&lt;/li&gt;
&lt;li&gt;And some? You have no idea.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That’s where &lt;strong&gt;envlens&lt;/strong&gt; comes in.&lt;/p&gt;

&lt;p&gt;✅ &lt;strong&gt;&lt;em&gt;What is envlens?&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
envlens is a lightweight tool that scans your project and identifies:-&lt;/p&gt;

&lt;p&gt;✅ Which environment variables are actually used in your code&lt;/p&gt;

&lt;p&gt;⚠️ Which variables in your .env file are unused or orphaned&lt;/p&gt;

&lt;p&gt;📦 Optional: Checks .env.example and reports missing or extra keys&lt;/p&gt;

&lt;p&gt;🧠 Bonus: Works with most JS/TS backends (Node.js, Next.js, etc.)&lt;/p&gt;

&lt;p&gt;💡 &lt;strong&gt;&lt;em&gt;Why is this helpful?&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
🧹 Clean up unused variables before deploying to production&lt;/p&gt;

&lt;p&gt;🔐 Avoid leaking secrets you’re not even using&lt;/p&gt;

&lt;p&gt;🤖 Automate env audits in CI/CD pipelines&lt;/p&gt;

&lt;p&gt;📚 Keep .env.example in sync with actual usage&lt;/p&gt;

&lt;p&gt;🛠 Perfect for teams, open source, and large monorepos&lt;/p&gt;

&lt;p&gt;⚙️ &lt;strong&gt;&lt;em&gt;How it works (1-min setup)&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
Install it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npm install envlens
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Run it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;npx envlens

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And it’ll output which variables are:&lt;br&gt;
Used ✅&lt;/p&gt;

&lt;p&gt;Unused ⚠️&lt;/p&gt;

&lt;p&gt;Missing 🔴&lt;/p&gt;

&lt;p&gt;🧪 &lt;strong&gt;Currently in Beta&lt;/strong&gt;&lt;br&gt;
I just released envlens as a public beta, and I’d love your feedback. Try it in your real-world project, and let me know:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What works?&lt;/li&gt;
&lt;li&gt;What’s confusing?&lt;/li&gt;
&lt;li&gt;What’s missing?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🔗 &lt;strong&gt;Get Started&lt;/strong&gt;&lt;br&gt;
📦 NPM: &lt;a href="https://www.npmjs.com/package/envlens" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/envlens&lt;/a&gt;&lt;br&gt;
🗨️ DM me or open issues — I’m actively improving it!&lt;/p&gt;

&lt;p&gt;🙌 If your .env has ever stressed you out, envlens is for you.&lt;/p&gt;

</description>
      <category>node</category>
      <category>backenddevelopment</category>
      <category>programming</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
