Official Zap.ts roadmap

[alexandretrotel]

Hey everyone,

I thought it would be great to publicly share the official roadmap for Zap.ts here.

Most of what follows is already reflected in the GitHub issues but I think it’s worth giving more context about the strategy, what I have in mind for Zap.ts, and how I’m prioritizing things.

The first big priority is building out the blog for SEO. It’s going to be based on MDX and Frontmatter, and since the integration is already partially done through the legal pages, it shouldn’t take long to finish. It will also allow to add internationalization right after.

Next up is adding payments. This is a critical piece for any SaaS, and for now, we’ll support Polar only. The reason is simple: it integrates cleanly with Better Auth, which we’re already using for authentication, so we keep things lean and cohesive.

After that, I’m focusing on RBAC and multi-tenant support. This is essential for any B2B SaaS. I want clean permission and auth logic that doesn’t become a nightmare to manage over time.

Then comes the modularization of Zap.ts itself. The goal is to break it down by feature, map out the dependencies each one uses, and understand how they interact. From there, I’ll encapsulate everything into plug-and-play functions. I’ll use tree-shaking to keep bundle size minimal and make things simple for this first approach. On top of that, I plan to use TypeScript AST manipulation to dynamically insert or strip code snippets as needed. If someone has a better approach, definitely speak up.

Outside of those core goals, there are a few nice-to-haves on my list. I want to improve local dev with Docker and Postgres pre-configured. I’d also like to add CLI features to scaffold API routes or other files, ship a basic onboarding template for SaaS projects, and include an admin page to test notifications, user management, and email flows.

Let me know what you think—and don’t hesitate to suggest things or open PRs if you want to help push this forward.