<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JavaScript on The Negation</title><link>https://www.thenegation.com/tags/javascript/</link><description>Recent content in JavaScript on The Negation</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 02 Aug 2024 21:54:10 +0000</lastBuildDate><atom:link href="https://www.thenegation.com/tags/javascript/index.xml" rel="self" type="application/rss+xml"/><item><title>Your package.json as a Credit Account</title><link>https://www.thenegation.com/posts/packages-credit-account/</link><pubDate>Fri, 02 Aug 2024 21:54:10 +0000</pubDate><guid>https://www.thenegation.com/posts/packages-credit-account/</guid><description>&lt;p&gt;It is quite easy to install a new &lt;code&gt;npm&lt;/code&gt; package into your project. I go one step
further, and insist on that actually it is &lt;em&gt;too&lt;/em&gt; easy.&lt;/p&gt;
&lt;p&gt;Every dependency in your project is like an expense on your credit account. And
that is &lt;a href="https://youtube.com/shorts/eIKqfujuxIQ?si=nEiLZG3siiZXKlQ6"&gt;not good&lt;/a&gt; if this credit account is not managed properly.&lt;/p&gt;</description></item></channel></rss>