Story Behind CottonJS

Started as a learning experiment born out of curiosity :- was an SSR framework in React too magical? I wanted to find out.

As I explored existing solutions, one thing stood out: the sheer number of dependencies in a typical React SSR setup. I wondered, could I build a framework that minimizes dependencies while still delivering a powerful SSR experience?

That’s how CottonJS came to life. I wanted to create a framework where features like routing, parameterized routing, route grouping, built-in API handling, middleware support, and module CSS were all custom-built; not just glued together from third-party packages. And all this while ensuring a great developer experience, including automatic page reloads without requiring extra dependencies.

But the biggest motivation? Transparency. I wanted everything needed to run CottonJS to exist within the project itself, not hidden inside dependencies. This way, any developer can dive into the code, extend it, modify it, and push the limits of what’s possible.

CottonJS isn’t just another SSR framework. It’s an attempt to bring back control to developers and let creativity take the lead.