<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nodejs on sugar, spice, &amp;terminal? nice</title>
    <link>https://terminal.space/tag/nodejs/</link>
    <description>Recent content in Nodejs on sugar, spice, &amp;terminal? nice</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 10 Jul 2025 15:00:30 +0000</lastBuildDate>
    <atom:link href="https://terminal.space/tag/nodejs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HowNot2 mock in Deno</title>
      <link>https://terminal.space/tech/hownot2-mock-in-deno/</link>
      <pubDate>Thu, 10 Jul 2025 15:00:30 +0000</pubDate>
      <guid>https://terminal.space/tech/hownot2-mock-in-deno/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://terminal.space/tech/hownot2-mock-in-deno/images/naoki-suzuki-JL3or092e-8-unsplash1.jpg&#34;&#xA;    alt=&#34;A funky crocodile made out of cups and other materials. It is sitting on top of some other cartoon character, wearing a read hat&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;A funky crocodile made out of cups and other materials. It is sitting on top of some other cartoon character, wearing a read hat&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;Mocking functions in deno is very limited, compared to NodeJS. Maybe, it&amp;rsquo;s so bad that it&amp;rsquo;s actually great. As your resident ruby-hater-in-chief, I&amp;rsquo;m here to tell you that code &amp;ldquo;magically working&amp;rdquo; comes at great cost. Today we&amp;rsquo;re going to learn about why modern javascript broke mocking, and why Deno refused to create magic to pretend otherwise.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
