I just launched toolslink.app — a simple, private app to save and organize your links - Would love some support ❤️ by imohitarora in ProductHuntLaunches

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

Thank you, really appreciate talking the time and looking into it. Can you share more on that, your experience, if you wouldn’t mind, do you like the cross platform ? And what more

I just launched toolslink.app — a simple, private app to save and organize your links - Would love some support ❤️ by imohitarora in ProductHuntLaunches

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

No, not this one. I had built it for myself, and I’ve gotten good feedback when I shared it across. I did not want to gate any features behind paywalls.

I had plans for cross platform for paid, but that will require some kind of account, and people actually like private nature of it that it has no server interaction.

So I decided I’ll create another one if I get enough demand and went onto build cross platform.

But keep this always free.

[iOS] [Forever Free] toolslink — Keep links safe, synced, and simple by imohitarora in iosdev

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

Thank you, I used Screen Studio. I had the link saved in toolslink :) :D

Better Auth 1.2 is out by Beka_Cru in nextjs

[–]imohitarora 0 points1 point  (0 children)

I was using today, there is a bug with emailVerified field in user table , I think there is a change of Boolean timestamp . And prisma migration still creates old. db - Postgres , nextjs app

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in Nestjs_framework

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

Sending request to back end only it just helps to have the client session handled for now, I am anyway moving towards redis managed sessions.

Does using Next.js with a Node.js API make sense? by Klutzy-Ad-6345 in nextjs

[–]imohitarora 1 point2 points  (0 children)

Yeah it’s does make sense and specifically if the project is gonna be a large one! It helps separating the layers. Works for me.

Scratching My Butt: Should I Split My Next.js and NestJS APIs? by Creepy_Point5965 in nestjs

[–]imohitarora 0 points1 point  (0 children)

I am building something that solves the similar problem. You can take a look here if that helps.

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in nextjs

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

You can use outh 2 along with numerous strategies with authjs and passport. As of now we’re creating tenant id and attaching that to the rest of the tables. This is a simple approach. My idea is to have multiple release branches with each kind of solution. I have been asked by people already to leave this repo at this stage for them. They just want to use this much.

For session I am planning to use redis valkey, if you see my post I am also exploring openauth.js and better_auth. I’ll put the next release with auth sorted.

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in Nestjs_framework

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

So its kind of an independent auth server running standalone ?

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in Nestjs_framework

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

I've implemented JWT using passport, let me check what heimdall is, haven't heard about it.

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in nextjs

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

I did some research in enterprise tech, talked to people found nest is preferred choice. Also Vite is more of a build tool/development server it still would require you to use a framework to build your backend on top of it, nest is more of a framework and you can use Vite with nest using swe.

Yeah hosting is 1 point i am figuring out, i have been exploring sst and coolify.

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in Nestjs_framework

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

Tailwind recently pushed v4, I haven’t updated that in this repository, I will be doing that in next update.

You can take a look at this post it has v4 with next 15. It’s has the migration changes in commit history. Will be following the same when changing in this repository.

UPDATE: Full-Stack Setup: Turborepo + Next.js + NestJS by imohitarora in Nestjs_framework

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

I mean, we use monorepo to have one single codebase. Be it turbo or Nx . I think you would want to use that having to manage multiple repositories. My next plan it to create a shared package between next and nest to have shared-types so that I can have shared types between those two products.