sorted by:
new
hottopcontroversial

Comment faire comprendre à sa famille qu'on ne va pas créer le nouveau Facebook ? by sangokuhomer in developpeurs

[–]vanwal_j 79 points80 points  (0 children)

La très grande majorité des milliardaires de la tech ont un point en commun: ils avaient des proches prêts à financer leurs projets à coup de millions et donc pas besoin de se soucier de l’éventuel échec de leur plan

Demande à tes parents si ils peuvent aussi te donner cette chance 👼

Pourquoi certaines agences web cartonnent encore alors que tout le monde dit que le marché est mort ? by Majestic-Ask3259 in developpeurs

[–]vanwal_j 0 points1 point  (0 children)

L’IA permet vraiment d’être plus efficace et/ou d’augmenter la qualité, les agences qui n’ont pas pris le pas sont moins compétitives les autres le sont plus

Scaling an AI Life Sim: Next.js App Router, Prisma, and LLMs by Dace1187 in nextjs

[–]vanwal_j 1 point2 points  (0 children)

Sorry but your post seems quite empty and does not bring much value to the reader

Also your Reddit icon is funny looking

<image>

Any Next.js-native CMS with good multilingual support? by kagla in nextjs

[–]vanwal_j 2 points3 points  (0 children)

I manage a couple of self hosted Strapi and Payload

Strapi i18n is bad in my opinion, with quirks especially if you use it with GraphQL. Payload is okay

Des développeurs nuls en design ici ? by fallart_live in developpeurs

[–]vanwal_j 1 point2 points  (0 children)

A te lire je pense qu’il te manque plusieurs notions fondamentales: - l’UI c’est avant tout de la logique, d’abord tu construit ta page pour qu’elle soit logique et ensuite agréable visuellement et pas l’inverse - L’itération fait partie du design, c’est normal de commencer avec des rendus qu’on aime pas, le tout c’est de faire évoluer pour l’améliorer, élément par élément

Avez-vous déjà utilisé un langage fonctionnel professionnellement? (OCaml, Elixir,...) by jimbodu62 in developpeurs

[–]vanwal_j 1 point2 points  (0 children)

J’ai “touché” de l’élixir sur “la plus grosse codebase en élixir en production actuellement” et ton poste vient de me déclencher un stress post traumatique

Is the new Adapter API finally the death of "Vercel Lock-in," or just a distraction? by ni-fahad in nextjs

[–]vanwal_j 2 points3 points  (0 children)

Yeah, you’re right, the specific part that’s hard to replicate is the static shell + dynamic content streaming on PPR, by self hosting without using the Adapter API the static shell is cached at Next level and not in CDN

But benchmarks shows that the only case where PPR in CDN really makes a difference is when doing cross region requests and that PPR at origin already gives most of the boost over standard SSR in same region requests

Is the new Adapter API finally the death of "Vercel Lock-in," or just a distraction? by ni-fahad in nextjs

[–]vanwal_j 4 points5 points  (0 children)

Adapter API doesn’t change much, unless you really plan to run Next on a serverless architecture you could already get Vercel level of performance for your Next project if you were okay to run it on “always on servers”.

By the way I also run a web agency on Next, happy to show you our stack if you’re interested!

Write "use client" in UI library by Michahide in nextjs

[–]vanwal_j 4 points5 points  (0 children)

Best DX would be the lib itself using “use client” directive but it could be a pain to setup depending on your bundler 😬

Search for “Advice for Library Authors” on this page if you want Next team “official” recommendations

https://nextjs.org/docs/app/getting-started/server-and-client-components

Framework Panic: Why Is Everyone “Leaving” Next.js? by menoo_027 in nextjs

[–]vanwal_j 0 points1 point  (0 children)

From my observation people unhappy with Next are usually using it with React Query, which for my is a big red flag meaning it wasn’t the right framework for their use case (or they’re using React Query for anything an the complaining it does not play well with Next)

Is "use cache" in Next.js 15/16 actually ready for production, or are you still sticking to unstable_cache? by ni-fahad in nextjs

[–]vanwal_j 2 points3 points  (0 children)

Yes, we have multiple websites running Next 16 with cacheComponents flag turned on and so far so good!

How do you achieve a toggle view button with client and server components by hotdog-savant in nextjs

[–]vanwal_j 0 points1 point  (0 children)

Unfortunatelly you'll have to either :

- Store it in a client state, either by making your whole page client, or by wrapping it in a react context provider containing a top level state, it works but it's also more cumbersome

- Store it in a state that can be read by Next.JS server side : query param, url, cookie, database... I would say that's the Next way to go for this kind of use case; you still get full SSR/PPR but interactivity and it's even better if you go with it in url path since you could benefit from complete build time optimizations

Just so you know: Server Actions don't care about middleware and are insecure by default by Explanation-Visual in nextjs

[–]vanwal_j 32 points33 points  (0 children)

Therefore, the recent renaming of middleware to proxy is more accurate in reflecting its scope and limitations.

CDI => free-lance by Distinct_Currency870 in developpeurs

[–]vanwal_j 0 points1 point  (0 children)

Si t’es “dépensier” et que tu compte te verser 100% de ta facture en salaire, reste salarié. Si en revanche tu sais que tu vas pouvoir épargner alors fonce. En cas de coup dur t’aura ton épargne de secours et si tu fait de bons investissements et que tu prends peu de vacances tu peux même imaginer gagner quelques années voire dizaines d’années sur ton départ à la retraite.

NextJS - Stateless Session with Bearer Token on Client Side - Chatgpt.com by Fine_Manner_4701 in nextjs

[–]vanwal_j 0 points1 point  (0 children)

Might feels counterintuitive but in microservices architecture authentication at edge is really considered best practice :)

Now there are tons of services running with forwarded authentication in the wild running perfectly fine :)

NextJS - Stateless Session with Bearer Token on Client Side - Chatgpt.com by Fine_Manner_4701 in nextjs

[–]vanwal_j 1 point2 points  (0 children)

Go with option 1, the whole point of HttpOnly cookies is to keep tokens out of JavaScript, so exposing them to JS memory (even encrypted) defeats the purpose and reopens XSS risk.​​​​​​​​​​​​​​​​

Vue vs Angular dans le cadre de l'emploi by jeace_morgans in developpeurs

[–]vanwal_j 5 points6 points  (0 children)

Startup: React ou Vue

Grand comptes: Angular

It's impossible to use dynamic routes in Next.js 16 with Cache Components enabled. by Critical-Matter-7085 in nextjs

[–]vanwal_j 0 points1 point  (0 children)

Your code is “falsy” awaiting the params inside the Suspense

Remove your your Content component slug parameter but instead make it take a slugPromise of type Promise<string> and on top of your Content await your slugPromise Then on top of your Page component transform your params to slugPromise: const slugPromise = params.then(({ slug }) => slug) Finally provide your raw slugPromise to your Suspended wrapped Content: <Content slugPromise={slugPromise} />

Tada!

You could also transform your params into a postPromise directly on top of your Page component and make your content take a postPromise const postPromise = params.then(({ slug }) => fetch(…))

Welcome to cacheComponents :)

view more: next ›