DEV Community: Shazin

I wrote a backend library for cloudflare worker and made it open source. Catch the full story.

Shazin — Thu, 27 Nov 2025 18:01:21 +0000

Shazin

Nov 27 '25

Introducing Cloud Rover. Turn Cloudflare Workers into Fully Functional Backends.

#webdev #serverless #javascript #cloud

Comments

3 min read

I wrote a backend library for cloudflare worker and made it open source. Catch the full story.

Shazin — Thu, 27 Nov 2025 17:35:56 +0000

Shazin

Nov 27 '25

Introducing Cloud Rover. Turn Cloudflare Workers into Fully Functional Backends.

#webdev #serverless #javascript #cloud

Comments

3 min read

Introducing Cloud Rover. Turn Cloudflare Workers into Fully Functional Backends.

Shazin — Thu, 27 Nov 2025 17:27:42 +0000

Last year I was looking for serverless solutions for building apps without having to manage servers by myself. I knew about cloudflare worker befor. But never thought it is built for running we services or building api on it. However upon using it I totally understood how it works. And thought all it needs is a routing system, proper request handling and some form of rules. That's all.

For those of you who don't know what cloudflare worker is here's a short note from cloudflare docs

A serverless platform for building, deploying, and scaling apps across Cloudflare's global network ↗ with a single command — no infrastructure to manage, no complex configuration

I started working on a lightweight middleware library to simplify things on worker. Initially I created it for my personal usage, didn't have any intention for sharing in public. However, I don't know if any new library exists now, but I just feel like I should share this, if anyone finds it helpful that will be great for me. So basically it just adds a lightweight layer on top of the worker and provides the followings

Easy routing
Seamless Request Handling: Process HTTP methods like GET, POST, and DELETE with built-in utilities.
Structured Response Management: Respond with JSON, text, or HTML without repetitive code.
Easy response handling (simplified from the original Response Interface )
Error handling
And other miscellaneous things like CORS handling, different kind of routes like schematic routes, standard handler function etc.

Most importantly it provides a standard structure which as of writing now by default cloudflare worker doesn't provide. When you create a new worker you’ll see something like this

export default {
  async fetch(request, env, ctx) {
    return new Response("Hello World!");
  },
};

And that's it from here you go full DIY mode. I created cloud-rover to simplify this process.

Using Rover

Rover is a very simple thing. You create a cloudflare worker normally then you install the npm package cloud-rover

Step-1

So start by creating a new worker and installing cloud-rover

# create worker
npm create cloudflare@latest -- my-first-worker
cd my-first-worker
# install cloud-rover
npm install cloud-rover

That's all you need as set-up.

Details Here

Step 2

Now go to the default index.js/ts file where you’ll see something similar I shared earlier.

Now you need to define

A router using createRouter method
Define a handler
Pass Rover as a response.

So instead of the default code provided by cloudflare we’ll use something like this

import { createRouter, RC, Rover, reply } from "cloud-rover";
// Define  a router
const router = Router([
  {
    path: "/",
    handler: index_handler,
  },
]);

// the index handler function
async function index_handler(rc: RC): Promise<Response> {
  return reply.text("Hello World From Rover!");
}

export default {
  async fetch(request, env, ctx): Promise<Response> {
    return Rover(request, router);
  },
} satisfies ExportedHandler<Env>;

That's all, you are now using cloud-rover. Just add more routes and functionalities.

Consideration

It might lack features and so does all softwares. I just added the essentials, if you think you can make it better feel free to contribute. If you need any feature you can create a feature request too. I made this library for my own usage and it might face bugs, feel free to create issues on github.

Open Source and Contributions

Like all meaningful tools, Rover is open source. It’s available on GitHub, and I’m excited to see how the developer community will use it to build amazing projects. Contributions, suggestions, and feedback are all welcome!

What’s Next?

Check out the official documentation for detailed guides, API references, and more examples. Or head straight to GitHub to explore the source code and get started. Or check out the NPM Package

Join the Journey

If Cloud Rover excites you as much as it excites me, consider starring the project on GitHub, sharing it with your network, or contributing code. Together, we can make Cloudflare Workers even more powerful.

Let’s redefine serverless backend development.
Thank you for reading.

Screw it! I've Developed My Own Static Site Generator!

Shazin — Thu, 15 Aug 2024 22:14:38 +0000

Web development nowadays has become so complicated thanks to the creators of thousands of new ways to do the same thing. In the early days of web development he had PHP and jQuery which did pretty much everything we needed. But well things have changed now.

Long Story Short

So, I was looking for a way to build my personal website. Which would have had some blogs and my project showcase that's it, no big deal right? Well, though the same thing as well. So, my initial thought was to use these as my tech stack

React
Firebase/Supabase
Tailwind CSS
Cloudflare Pages for deploying

Well, this could be the happy ending but... 🙂

As I've already stated I will need a blog section and ironically blogs and react doesn't go well together. Since React is basically for building WebApps not content driven websites. Now those who don't know why here's a summary from chatGPT

Why React is Not Suitable for Content Driven Sites

ChatGPT Said,

React is not ideal for content-driven sites primarily because it relies on client-side rendering, which can negatively impact SEO and initial page load times. Content-driven sites benefit from server-side rendering (SSR) or static site generation (SSG), which React doesn't handle out of the box. Tools like Next.js or Gatsby, which extend React, are better suited for these needs.

Next Target: NextJs

Well it's obvious that I need SSR for blog site since I wanted a good indexing by search engines and a professional social media link previews. NextJs could give me both of those, but there's still a problem, and it's kind of a personal one.

See, I always loved using cloudflare pages and wanted to stick with that, besides I wanted cloudflare's free email routing to have a custom email address attached to my domain thus reducing the cost.

NextJS at Cloudflare

I tried deploying nextJS site to cloudflare pages via their official documentation. Well, things didn't go well. I wasn't able to deploy there I tried hours finding solution and nothing worked. Let's just say nextJS and cloudflare didn't go well together for me. So if anyone from Vercel or Cloudflare reading this correct me if I'm missing something.

Well, at this point I was hopeless and the last option I had was SSG.

Next Solution: SSG

Now SSG is good, and I understand the importance here. The problem is I've never worked with SSG before and there are multiple routes to through. There are things like Hugo, Gatsby, Astro blah blah. And probably more. Now I wasn't familiar with any of those and at this point I was so frustrated that I wasn't willing invest a bit on learning a new tool for a simple blog app. So I was like f*$k it I'll do my own thing.

Creating My Own Static Site Generator.

Few points why I decided to develop my own static site generator

I was frustrated (of course lol)
Since I am making my own tool for my own thing, I will have the full control over how the pages will be generated. How will they look like.
I like to reinvent.
I had free times to spend.

The Plan

The plan was going old fashioned way of creating website. Separate articles will have their own html pages.

Here's the full outline:

I'll be writing on palin Markdown files
Use python to parse the markdown into plain HTML
I will already have a template where different sections will be dynamically injected.
Also I'll have a config file corresponding to the article. So the file hierarchy will kinda look like this

articles/
├── art-1
│   ├── art.md
│   └── config.json
├── art-2
│   ├── art.md
│   └── config.json
├── art-3
│   ├── art.md
│   └── config.json
└── art-4
    ├── art.md
    └── config.json

Hence, each post will have it's own folder and the folder will have the config.json and art.md , The python script will take the template.html and insert dynamic contents to that HTML template, for instance the post title, slug, thumbnails from the config file and main article from the parsed markdown file. Most importantly it will dynamically generate meta tags for SEO and social medias.Afterwards, it will write the changes to a file called art/<post-slug>.html so that the post link will be example.com/art/slug.

How was it integrated?

Well so I've developed a CLI interface for interacting with the generator. I've named it fit you know as in F it. It has the following commands or options:

$ ./fit --help
fit: also known has f**k it build system
A build system for my personal site developed by Shazin

USAGE
     fit <action> <argument>
COMMANDS
    init                Creates a new post template at articles/art-[n]
    build art-<n>       Builds the specified article
    sync                Syncs the global articles index to homepage
    uploader            Launches the GTK GUI image uploader
    upload <file_path>  Uploads the specified file to firebase
    deploy              Deploys local changes to remote repository
    help, -h, --help    Displays this help menu

Deployment mechanism

So, like I said I wanted to use Cloudflare pages for deploying. Basically what I've done is I've created a branch called prod and whenever the ./fit deploy command is run it will basically copy all the necessary files to the prod branch and push the changes to github. Then, cloudflare will automatically build and redeploy the changes.

Handing images

In order to handle images or any static files I have used firebase storage, the ./fit uploader will pop open a GTK based GUI uploader from which I can upload an image and it will give me the public url which I can than copy, Here's how it looks:

Upload Interface

Post Upload Interface

CLI Interface

There's also a CLI Interface which can be used by ./fit upload <filepath this was an option for cases where I don't have access to a GUI interface. This allows me to publish or edit articles from my phone as well using terminal emulator like Termux

Dynamic Ambient Bcakground

So, I thought when I am the one handling all the building and generation myself I can definitely do some cool stuffs with it, so I've added a dynamic colored ambient background to each post. The idea was to pick an average color from the thumbnail image and then darken it and use it as the background. I've also picked a primary color for the links and buttons from the thumbnail image as well and honestly to me, it looks really cool, here's an screenshot

Comments and Discussion

Since I was working with basically no database or no backend service at all, I had to choose an external service for this and what else does this better than Disqus .

Was it Worth It?

Well, to be honest like I said I was spending some free times, so yeah it was definitely worth it, and it didn't take me long time to be honest I've spent 2-3 days for this full project and really had fun building something creative.

Wrapping Up

So, I've had really fun experience with this project and will hopefully do more improvements and add more functionalities to it. Right now it's so basic and simple which was what I wanted. If you like this project or want me to open source it please let me know. Oh and here's the link of the site I was screaming about shazin.me Thanks for reading.