fragno

I'm working on a toolkit for building "full-stack" libraries. I.e. libraries that bundle frontend hooks, backend routes, and a database schema into a single package. On top of this I built a library for email that listens to Resend webhooks and stores the email (with thread information) directly in the user’s database. This is a more complete package than what Resend themselves could provide with their backend-only library. https://github.com/rejot-dev/fragno https://fragno.dev/fragments/resend

For a project I'm working on, I needed Google Forms/Typeform functionality that is built into the application. Rather than building it directly into the app, I decided to build it as a TypeScript library that anyone can use. The library is full-stack, meaning it comes with database schemas for the form/response tables, backend route handlers for creating/updating forms and collecting form submissions. I use JSONForms [0] to define how forms should be rendered, and implemented a new JSONForms renderer for shadcn/ui projects. (But you can use any other compatible renderer). An overview of the features: - DB Schemas, request handlers, and frontend hooks included - Form builder shadcn/ui component with Google Forms-like UX - Integrates with any TypeScript stack - Form validation using JSON Schema + Zod In the future, I might look at creating

I'm working on a meta framework for building "full-stack" libraries. I.e. libraries that bundle frontend hooks, backend routes, and a database schema into a single package. This allows library authors to do more, like defining webhook handlers and (simple) database operations. The idea is to move complexity from the library user to the author, making (API) integrations easier. I think libraries being able to write to your database is a pretty powerful concept, and can enable a number of interesting use cases. https://github.com/rejot-dev/fragno

I'm working on a meta framework for building "full-stack" libraries. I.e. libraries that bundle frontend hooks, backend routes, and a database schema into a single package. This allows library authors to do more, like defining webhook handlers and (simple) database operations. The idea is to move complexity from the user to the author, making integrations easier. I think libraries being allowed to write to your database is a pretty powerful concept, and can enable a number of interesting use cases. https://github.com/rejot-dev/fragno

We've got a simple AI chat fragment in our repo: https://github.com/rejot-dev/fragno/tree/main/packages/chatn...

Hi HN, I’ve been building 'Fragno', a toolkit for building full-stack TypeScript libraries that work seamlessly across frameworks like Next.js and SvelteKit. Traditional libraries are built to integrate on either the frontend or backend. Glue code ends up being re-implemented for every project: API routes, documentation (OpenAPI), client-side integration, etc. With Fragno, you can write libraries that include API routes and client-side hooks/logic. Users can integrate a Fragno library into their application with just a couple of lines of code. This embeds the API routes and lets them immediately use the library’s functionality from the frontend. A Fragno library integrates end-to-end: type-safe from reactive hook to backend logic. It supports React, Vue, Svelte, Next.js, React Router, Nuxt, SvelteKit, and more. The need for a full-stack l