A lot of people have been asking me lately about the ETA of the new version of @supastarter. This has been creating some pressure on me, because I always feel like needing to justify that it is not ready... π₯²
Setting up a new application including auth within 2 hours and now trying to find out why dotenv-cli won't read my local env file for fucking 4 hours π€―π
I try to fix them or get in touch with the maintainers and library authors. Thatβs why the implementation of the current version takes so long. Donβt want to release a version that is not production ready yet.
Incredible, I just saw that the @supastarter twitter account now has +1k followers π€― Thanks so much to everyone who has been supporting me on this journey and let's see where we can take this next π
Translations with @nextjs for the new @supastarter version are now finally implemented thanks to the awesome work of @aralroca on next-translate! Very nice API for RSC and client components π₯
It's just incredible how much me being active on twitter impacts the sales of @supastarter π I didn't make one sale in the last two weeks and after a very active weekend on Twitter, I just got 3 in a row π
For the next version we went the extra mile to build an abstraction layer for auth, so you can pick your favorite auth provider and it will work right out of the box π₯
Even after hundreds of deployments on @vercel the UX of this flow is just phenomenal π₯
Just deployed the first draft of the new landing page from the new monorepo structure built with @turborepo. Next up is the SaaS app part. Let's go! π
Now this is what #buildinpublic really is about for me. Not only sharing the positive things and success stories, but being honest and open about your journey. Sometimes things don't work out and that's totally fine. But it's part of the journey to become who you want to be.
The new version is also including storybook for easier component development. Still trying to figure out how to get next/font configured in there though π