<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Node.js on Nalar</title>
    <link>https://nalar.dev/tags/node.js/</link>
    <description>Recent content in Node.js on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/node.js/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Node.js Chooses Between .mjs, .cjs, and .js Module Formats</title>
      <link>https://nalar.dev/nodejs-mjs-cjs-js-module-formats/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/nodejs-mjs-cjs-js-module-formats/</guid>
      <description>&lt;p&gt;Node.js can execute JavaScript through two module systems: ECMAScript modules (ESM) and CommonJS. The filename is one of the signals that selects between them, which is why files such as &lt;code&gt;postcss.config.mjs&lt;/code&gt; appear in projects even when most source files still end in &lt;code&gt;.js&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The important detail is that &lt;code&gt;.mjs&lt;/code&gt; is not a different JavaScript language. It is an explicit instruction to Node.js: parse and load this file as an ES module.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
