<?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: vazmat</title>
    <description>The latest articles on DEV Community by vazmat (@vazmat).</description>
    <link>https://dev.to/vazmat</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%2F3288766%2Fd22fae4a-0439-4ac9-a6c4-3c5bd0e40dec.png</url>
      <title>DEV Community: vazmat</title>
      <link>https://dev.to/vazmat</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vazmat"/>
    <language>en</language>
    <item>
      <title>Introducing JSONExpress</title>
      <dc:creator>vazmat</dc:creator>
      <pubDate>Mon, 23 Jun 2025 21:44:04 +0000</pubDate>
      <link>https://dev.to/vazmat/introducing-jsonexpress-2m0h</link>
      <guid>https://dev.to/vazmat/introducing-jsonexpress-2m0h</guid>
      <description>&lt;p&gt;As developers, we've all felt the pain. You're building a beautiful new UI, your components are ready, but you're blocked. The backend API isn't finished. So what do you do? You start hardcoding data, creating messy mock objects, or wrestling with complex server setups just to get some fake data.&lt;/p&gt;

&lt;p&gt;This friction in the early stages of development slows us down and kills momentum.&lt;/p&gt;

&lt;p&gt;I wanted a better way. A tool that was as simple as &lt;br&gt;
&lt;code&gt;cd my-api/ &amp;amp;&amp;amp; start-server&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Meet JSONExpress
&lt;/h2&gt;

&lt;p&gt;I'm excited to introduce &lt;strong&gt;JSONExpress&lt;/strong&gt;, a zero-configuration mock REST server that lets you focus on your front-end, not your fake back-end.&lt;/p&gt;

&lt;p&gt;The idea is simple: &lt;strong&gt;Each JSON file in your directory becomes an API endpoint.&lt;/strong&gt; The filename defines the resource path.&lt;/p&gt;

&lt;p&gt;Let's see it in action. Imagine you have a project folder structured like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;my-api/
├── users.json
├── posts.json
└── comments.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each file contains a simple array of JSON objects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;users.json:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[
  { "id": 1, "name": "Ada Lovelace", "email": "ada@example.com" },
  { "id": 2, "name": "Grace Hopper", "email": "grace@example.com" }
]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;posts.json:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[
  { "id": 101, "title": "On the Analytical Engine", "authorId": 1 },
  { "id": 102, "title": "Compiler Theory", "authorId": 2 }
]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now, let's fire up the server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Installation &amp;amp; Usage:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;# 1. Install the CLI tool from npm
npm install -g @json-express/core

# 2. cd into the directory containing your JSON files
cd my-api/

# 3. Run the magic command
json-express
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Instantly, you get a running server. JSON Express scans the directory and creates your API. The console will show you something like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;🚀 Server running on port 3000

Get users:     GET     http://localhost:3000/users
Get one users: GET     http://localhost:3000/users/:id
Search users:  POST    http://localhost:3000/users
Create users:  POST    http://localhost:3000/users
Update users:  PATCH   http://localhost:3000/users/:id
Delete users:  DELETE  http://localhost:3000/users/:id

...

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

&lt;/div&gt;



&lt;p&gt;You now have a complete REST API with full CRUD support for each resource:&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Another One?
&lt;/h2&gt;

&lt;p&gt;The world of mock API servers is rich with great tools. So why build another? My vision for JSON Express is to create the most intuitive, extensible, and developer-friendly experience possible, starting with a clean, file-based structure. This is just the beginning. (I'll be writing more about the philosophy and roadmap soon, so stay tuned!)&lt;/p&gt;

&lt;h2&gt;
  
  
  Get Started Today!
&lt;/h2&gt;

&lt;p&gt;Give your workflow a boost and take JSON Express for a spin.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Install it:&lt;/strong&gt; &lt;code&gt;npm install -g @json-express/core&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Learn more:&lt;/strong&gt; Check out the official website at &lt;a href="https://jsonexpress.com/" rel="noopener noreferrer"&gt;jsonexpress.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contribute &amp;amp; Star:&lt;/strong&gt; The project is open-source! Find it on &lt;a href="https://github.com/vaz-matri/json-express" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;, give it a star, and feel free to open issues or PRs.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Let me know what you think&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
      <category>api</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
