Kirimase

People say AI is going to replace programmers, but thankfully @nicoalbanese10 came through with @kirimasedev . Your CLI tool has been a game-changer for building Next.js apps!

@kirimasedev is goated. definitely try it out if you starting a new nextjs project

@ste_alexandru updated!

@kirimasedev Amazing CLI but maybe you should change the npx / bunx / etc shadcn-ui@latest command with shadcn@latest cause the CLI command got changed.

Boilerplates are dead. Time for code gen. Few interesting projects: - shadcn CLI ui.shadcn.com/docs/cli - Kirimase kirimase.dev - v1 x.com/pontusab/statu…

@EmmerichBret In the video, I'm using /src directory. It doesn't have any impact on the application. I suggest following the written guide vs. the video as it's much easier to follow! kirimase.dev/the-tutorial

@kirimasedev Yours is different, i posted mine above, ill post it again below this

@kirimasedev is this the structue? It’s softener from the tutorial and has basically duplicated (looking) folders, like auth in different places

@EmmerichBret Did you select the same packages as the tutorial? If so, then it will be the same 😊

@kirimasedev So, this is the correct files? The tutorial seems different .

@EmmerichBret so for auth, you have the auth pages / api routes, the auth components, and then the auth utility functions functions

@EmmerichBret files are grouped at the top level as - pages (/app) - components (/components) - utilities (/lib) - configuration (/config) then you have sub groupings for their function within the app ie. auth, db, api etc.

@EmmerichBret that's my suggested solution for now!

@kirimasedev Should I use pnpm?

@kirimasedev I just created a project, but it’s erroring, saying packages arnt found, that I didn’t select to use. I really want this to work Icons are ruining the whole project, Just because they’re not found in packages. Is there an update coming? This has massive potential

@0xMishra never too late!

Could it be that I've stumbled upon @kirimasedev too late in the game?

@blakegreendev @webdevcody yes! one command and you're ready to go 😊

@webdevcody Use @kirimasedev and skip the initial setup 😅😎

man... I'm working on a tutorial using next-auth with drizzle and I can say is this initial setup is a pain in the ass. next-auth docs still have pages routes sprinkled everywhere even though the app router has been out for a year+ drizzle-studio requires me to constantly restart after running a migration (unless I'm missing something), getting the user id on the session object in next-auth requires adding all this extra callback stuff and overload the session type drizzle has two separate ways to interact with the tables db.query.tablename and db.insert(tablename) (like why is the interface between query and insert totally different?) add on top I'm using docker-compose to spin up a postgres database locally because these database service provides can't be trusted to not drop their hobby plans add on top of that I'm using app router so the viewer now needs to understand why I'm refactoring random components from my page.tsx into it's own file just so I can not have it crash. throw in react-hook-form with shadcn's form components and everything starts to look like hieroglyphics. no wonder people from Laravel and Django look at our stack and laugh their ass off when they can have an entire application ready to go from scratch in 5 minutes. I'm about to just sell a next.js starter kit and sell it for $100.

Just finished the @kirimasedev tutorial, and I'm lost for words. I've been longing for a CLI-like tool for Next for so much time... and this is just gold💫

kirimase is amazing, precisely because it's not using AI for backend code-gen you define your data model, and it generates: orm schema, types, zod schemas, server actions & api routes predictable, with best practices in mind, packaged and ready to use in your UI in seconds 😊

new @kirimasedev update (0.0.57) Now supporting @lucia_auth v3 (powered by server actions) It’s so fast, you can get your full stack @nextjs app deployed to the web (w/ @vercel) in literally 2 minutes 🤯

been looking for an easy way to try @kirimasedev? I present you, "Kirimase: The Tutorial" everything you need to know, in one tutorial try it and see how it's the fastest way to build your next @nextjs app! kirimase.dev/the-tutorial

@nicoalbanese10 @kirimasedev @vercel kirimase is amazing, great work!

I thought our “full-stack Linktree clone in 15min” was impressive With @kirimasedev’s recent updates, you can now do it in just 8! Truly bonkers. I think this could be the fastest (and most fun) way to build with @nextjs 👀

another big @kirimasedev update (v0.0.53) - landing page generated by default (thanks @v0) - upgraded toasts to @emilkowalski 's sonner - now using route groups by default routes are split into (app) or (auth) allowing for top level auth check encapsulation 👌🏻

Fun and fast - that's what it's like building with @kirimasedev and @nextjs Kirimase does so much of the heavy lifting that it almost feels like you're writing pseudocode Here is an unscripted video of me adding a new feature to yesterday's demo app