Live data from Hacker News

Show HN: Typebase – A single-folder back end you write in TypeScript

typebase.io

51–60 of 63 posts

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#53
I tried it on small project. A lot of promising ideas. I don't even care it is so new.

What didn't work for me is the build step. In a bigger project it should be normal to have this but I really love to interactively build and having to restart and rebuild after each change is issue for me.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#54

I tried it on small project. A lot of promising ideas. I don't even care it is so new. What didn't work for me is the build step. In a bigger project it should be normal to have this but I really love to interactively build and having to restart and rebuild after each change is issue for me.

I'm glad you liked it! Were you using a local build or were you uploading to a server on each change?

For the local build we have the 'generate-server --watch' command and I want to add an option so on every rebuild it runs another command, something like 'generate-server --watch --command "pnpm run dev"' so on every change the server runs the latest version of the code.

For when you upload to a server theres no much we can do because the builds on the server take too long, something we have on the roadmap is having our own server provider and the number 1 priority is that is so fast that you can deploy a new version on every local change.

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#55

Scratching my head a little bit here, I'm not sure how this differs from NextJS (or Vite) with a layer of drizzle & better-auth. Not that that layer isn't important. We ended up building something like this at Ingram, nextkit: https://github.com/ingram-technologies/nextkit - but we distribute it as a set of micro libraries that work well together rather than a unified framework. (Auth is nk-auth, built on top of bett…

[flagged]

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#56
post #4

I’ve been curious about trying the Supabase type of RLS model for an app but haven’t yet. I like the idea of the db defined api like postgraphile and hasura but had trouble with testing and ergonomics. This looks pretty nice though, it’s cool that you’re thinking about ergonomics for working with coding agents. I feel like a hard thing with that rn is that everyone is kind of figuring out different workflows for AI c…

[dead]

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#57

Earlier quoted context omitted.

I see no code there to automatically pick D1 for the DB when you deploy to Cloudflare. On Cloudflare, it should use the `@neondatabase/serverless` driver configured here https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa...

Hey! For now we only support Neon but the idea is too add more DB providers soon. I wanted to build a "base layer" to show that Typebase is versatile enough, I'll add D1 to the priorities

[dead]

Re: Show HN: Typebase – A single-folder back end you write in TypeScript

#58
post #37

I have deployed and maintained plenty of diff setups on GCP, AWS, colo, and I have also used AI for coding, my concern is do we really trust AI to do prod deploy and maintenance of the backend yet? Not to mention what are the limitations here, someone already mentioned queues? But for a straightforward site with limited complexities, it might be cool to try out.

What about you configure your aws cli and tell the agent which command to run for deployment? I found that useful since I don't have to expose any secrets to it, just a static set of commands
Post reply on HN