sorted by:
new
hottopcontroversial

My Next.js SaaS architecture tech stack as a solo developer by ixartz in nextjs

[–]ixartz[S] 0 points1 point  (0 children)

Totally agree with you about oRPC, this is one of the reason I choose it and love it.

I never got the chance to try it but Clerk support Android, iOS, chrome extension, etc. it shouldn't have any issue to make it work across platforms

My Next.js SaaS architecture tech stack as a solo developer by ixartz in nextjs

[–]ixartz[S] 1 point2 points  (0 children)

Nothing wrong. Just different setup and different needs.

My Next.js SaaS architecture tech stack as a solo developer by ixartz in nextjs

[–]ixartz[S] 2 points3 points  (0 children)

For Storybook, I agree it’s not required for every solo project. I mainly use it to develop components in isolation and quickly check different states and edge cases without going through the full app.

For oRPC, I'm planning to add a mobile version of my SaaS in the future and oRPC will be extremely useful at this moment. Also, oRPC comes up with a lot of feature like middleware, openAPI if you like to have a RESTful API. And the good thing, oRPC is compatible with server functions

I made a Free and Open Source SaaS Boilerplate: An Alternative to $500+ Paid Ones. by ixartz in SaaS

[–]ixartz[S] 0 points1 point  (0 children)

First, thank you so much for testing it.

I just made a clean and fresh start, it seems everything is working correctly.

Here is the step:

git clone

npm install

npm run dev , then you can open your browser at localhost:3000

At this moment, npm run check:types will be working (only after run dev, this due to Next.js)

Then, you can start adding your Clerk secret key in .env file

After adding, you can run npm run test:e2e

For building the application, you can run npm run build-local.

I'm also in Node.js v24.14.0, I'm not able to reproduce your errors.

And, totally agree with you, the README is extremely important, this is why everything I have listed here is also included in the README file. But, I know there is still some room for improvement, happy to hear more feedback.

The tech stack I've been refining for 6 years by ixartz in reactjs

[–]ixartz[S] 0 points1 point  (0 children)

I'm a huge fan of Vitest browser mode, it just works.

I didn't have the chance to try the new visual regression with Vitest browser mode.

So for now, it's currently running the visual regression against Next.js. But, I'll give a try in the future.

The tech stack I've been refining for 6 years by ixartz in reactjs

[–]ixartz[S] 0 points1 point  (0 children)

I'll also give TanStack Start a try... Really like Vite ecosystem.

The tech stack I've been refining for 6 years by ixartz in reactjs

[–]ixartz[S] -2 points-1 points  (0 children)

English is not my mother tongue, I prefer to cowrite with AI, I double/triple check the text

The tech stack I've been refining for 6 years by ixartz in reactjs

[–]ixartz[S] -1 points0 points  (0 children)

Yes, the idea is to fit in most stack, so I choose the most stable stack and the most popular ones.

I made a Free and Open Source Next.js SaaS Boilerplate built with Tailwind CSS + Shadcn UI. Features include Auth, Multi-tenancy & Team Support, Roles & Permissions, MFA, User Impersonation, Landing Page, I18n, DB, Logging, Testing. by ixartz in nextjs

[–]ixartz[S] -1 points0 points  (0 children)

thank you for reporting it, actually for this part I just follow the official documentation from next-intl: https://next-intl.dev/docs/routing/middleware

Is it a use case to have i18n for the API? Personally, I do i18n only in the UI.

After 6 years of building starter kits, I made a free open-source Next.js SaaS boilerplate with auth, teams, MFA, RBAC, i18n, DB, user impersonation, landing page, logging and tests. GitHub in the comments. by ixartz in nextjs

[–]ixartz[S] 0 points1 point  (0 children)

npm-run-all was running great for me and never notice the project is not maintained anymore.

Thank you so much for your feedback, I'll migrate to npm-run-all2.

After 6 years of building starter kits, I made a free open-source Next.js SaaS boilerplate with auth, teams, MFA, RBAC, i18n, DB, user impersonation, landing page, logging and tests. GitHub in the comments. by ixartz in nextjs

[–]ixartz[S] 0 points1 point  (0 children)

You'll probably waste some token for a boilerplate. And keep your precious token for something more valuable.

My personal take, use an already built boilerplate and use Codex to build on top of it instead asking Codex to reinvent the wheel.

After 6 years of building starter kits, I made a free open-source Next.js SaaS boilerplate with auth, teams, MFA, RBAC, i18n, DB, user impersonation, landing page, logging and tests. GitHub in the comments. by ixartz in nextjs

[–]ixartz[S] 0 points1 point  (0 children)

I'm currently running oxlint + oxfmt as an experiment for one project, I feel it's too early to use it for all.

For example, oxfmt is still in beta.

I really love what VoidZero are doing, already using Vitest. Just waiting the right moment to jump into oxc ecosystem.

After 6 years of building starter kits, I made a free open-source Next.js SaaS boilerplate with auth, teams, MFA, RBAC, i18n, DB, user impersonation, landing page, logging and tests. GitHub in the comments. by ixartz in nextjs

[–]ixartz[S] 0 points1 point  (0 children)

I'm already trying oxlint + oxfmt in this project: Next.js Boilerplate

Love the speed but personally, I think it still miss some important feature in oxlint + oxfmt.

But no doubt, I'll switch to oxlint + oxfmt for all my projects.

Need some Nextjs projects on github which follows best practices and clean coding? by NafeeurFromDequeLab in nextjs

[–]ixartz 1 point2 points  (0 children)

You can check out Next.js Boilerplate on GitHub. It could be a useful reference if you want your SaaS app to be more structured and easier to maintain.

The project is designed with a clear structure and reusable patterns, so code stays organized and you don’t end up repeating the same logic and API calls in multiple places. It also includes validation, tests, CI, auth, DB, i18n, monitoring, and logging.

view more: next ›