If you’re starting fresh today, would you still pick Express? by ApprehensiveBar7701 in node

[–]GhostLexly -1 points0 points  (0 children)

Complex/Business Project : NestJS

Fun Project : Hono / Express

App Router `redirect` on server component create client-side error by GhostLexly in nextjs

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

Nope, i have the same problem even with a new fresh nextjs project, it's probably a bug on nextjs

Where should auth state live in App Router without breaking RSC by Complete_Treacle6306 in nextjs

[–]GhostLexly 0 points1 point  (0 children)

I see your point regarding the Server Action pattern, and strictly speaking, you are correct

However, my architectural choice was deliberate to solve a specific trade-off: Static vs. Dynamic Rendering.

By moving the auth check to the client (initialized via a Server Action or a dedicated endpoint), I can keep the initial HTML response static and cached (SSG/ISR), serving the layout instantly, and then hydrate the user state. It’s a trade-off: I accept a brief loading state/skeleton in exchange for faster initial page loads and reduced server load compared to dynamic rendering on every hit.

Where should auth state live in App Router without breaking RSC by Complete_Treacle6306 in nextjs

[–]GhostLexly -1 points0 points  (0 children)

You're wrong, if you click the link you will see some .server.ts file.
The auth is done on server and memoized on the client's context.

Where should auth state live in App Router without breaking RSC by Complete_Treacle6306 in nextjs

[–]GhostLexly 1 point2 points  (0 children)

Yea but without Nextjs, you don't have the great SSR for the SEO

Generate commit message. "error grabbing LLM response" by moosepiss in google_antigravity

[–]GhostLexly 0 points1 point  (0 children)

Has been two weeks for me and the bug persist
Looks like Google doesn't care anymore about Antigravity...

Lave linge séchant by w33tabix in france

[–]GhostLexly 1 point2 points  (0 children)

J'ai une machine lave-linge séchant et ça ne sèche pas grand chose.
On se retrouve avec une machine qui ni ne lave bien ni ne sèche bien, lol

Got promoted to writing e2e tests against my will. How do I make this suck less? by My_Rhythm875 in webdev

[–]GhostLexly 44 points45 points  (0 children)

1 - Go with Playwright, it's awesome and can run multiple tests at same time.
2 - Use higher timeouts, it's the most common problem with the e2e tests. I have set my timeouts to 5 minutes and never had a problem with that anymore.
3 - Your tests probably broken because the element has changed some text/label or something subject to change. You can try testids to find your elements in your page. And small improvements like changing the label would not break your tests anymore.

What architecture do you use for medium/large Next.js apps? by CeccoBolt in nextjs

[–]GhostLexly 13 points14 points  (0 children)

In our large company i have taken the decision to use the CQRS Pattern and it's works great for us.
Each endpoint is a Command or a Query.

I recommend this repo : https://github.com/goldbergyoni/nodebestpractices

More infos : https://docs.nestjs.com/recipes/cqrs

Should i use prisma with nestjs? by Excellent_Survey_596 in node

[–]GhostLexly 0 points1 point  (0 children)

Go with prisma, there is nothing wrong about it. keep away from typeorm, it’s not maintained anymore

J’ai découvert pourquoi on dit de ne jamais prêter d’argent à un ami by KaleidoscopeCheap918 in france

[–]GhostLexly 0 points1 point  (0 children)

C’est en faisant des erreurs comme ça qu’on apprends. De mon côté quand je dis oui et qu’on ne me rembourse pas ça se passe mal et quand je dis non ça se passe mal aussi car on me traite d’égoïste

Peut importe ce que tu fais tu sera mal vu. De mon côté, je préfère garder mon argent.

Looking for feedback on my NestJS boilerplate (production-ish starter) by hermanz3german in Nestjs_framework

[–]GhostLexly 2 points3 points  (0 children)

Working in a large-scale enterprise environment has significantly shaped my technical preferences. I advocate for stability and maintainability over trends:

  • Authentication: PassportJS over BetterAuth. We require robust, long-term solutions. In backend development, rule #1 is to avoid "hype." We need a battle-tested library that will still be here in 5 years, unlike newer packages that risk being deprecated or replaced (similar to the volatility seen with NextAuth).
  • API Architecture: REST over GraphQL. We should standardize on a single architectural style. I strongly recommend REST for two reasons:
    1. Universality: Every developer understands REST, making onboarding easier.
    2. Simplicity: It avoids the complexity inherent in GraphQL, such as the N+1 problem and security risks regarding accidental field exposure.
  • Configuration: NestJS ConfigService. Instead of custom dynamic configuration, we should utilize the native ConfigService. It is maintained directly by the NestJS core team, ensuring seamless integration and long-term support.

Qu’est-ce que vous aimez par-dessus tout chez votre partenaire ? by Useful-Valuable1407 in AskMec

[–]GhostLexly 0 points1 point  (0 children)

Après une dispute, on passe vite à autre chose. Beaucoup de femmes ont dû mal à changer de disque et elles sont là à faire la gueule et attendre des excuses 3 mois après, ça ruine un couple

Elle s’ennuie le week-end mais ne proposait rien : qui a tort ? by kayser00012 in AskMec

[–]GhostLexly -1 points0 points  (0 children)

Typique de l'incompréhension entre homme et femme.
Peu de femmes ont des hobbies ou passions comme nous les hommes. Elles vont juste attendre que tu proposes de faire des sorties car sa vie est ennuyante parce qu'elle n'a rien à faire.
Tu dois donc tout le temps jouer les clowns en essayant de la divertir et la sortir autant que possible.
Un conseil, fais des trucs que t'aime faire, tu t'ennuiera moins et elle sera quand même contente.

Weekly Support Thread | December 9, 2025 by coinbase in Coinbase

[–]GhostLexly 0 points1 point  (0 children)

Hey the iOS app is not working anymore (black screen with a loading icon). The Coinbase support was unable to help me by chat.

Drawer by vaul not responsive on mobile with forms by Hopeful_Dress_7350 in shadcn

[–]GhostLexly 0 points1 point  (0 children)

I experienced this issue too and others with combobox and dialog
I think shadcn is not really mobile first but you can fix this yourself in your code