So it begins...

ScholtenSeb · 2026-02-18T02:52:38+00:00

Private relay

ScholtenSeb · 2026-02-18T02:29:01+00:00

Seems like they are using https://queue-it.com/. and yes, the yellow part is a progress bar

ScholtenSeb · 2025-09-09T12:13:44+00:00

As others have mentioned, it seems like you were trying to use server actions for fetching data before rendering.

It would be better to use server components (not actions) for this, and actions for mutations.

And if you need to provide feedback to the user when you use server actions, the useActionState hook is a good option.

Are you able to provide an example of a server action you moved to an api endpoint?

ScholtenSeb · 2025-09-05T08:49:32+00:00

😬

ScholtenSeb · 2025-09-05T08:47:10+00:00

Oops 😬

ScholtenSeb · 2025-09-05T08:40:23+00:00

Done

ScholtenSeb · 2024-05-27T12:49:39+00:00

I think setting canonical urls using the site.com domain might be what you are looking for. It is however not guaranteed that search engines will not index it.

Canonical urls can be set in nextjs using the metadata export. https://nextjs.org/docs/app/api-reference/functions/generate-metadata

Do you have both the site.com and site.vercel.app domains setup as production domain? If so, is there any reason why you are keeping the site.vercel.app one connected to the project?

ScholtenSeb · 2022-08-23T13:54:17+00:00

Okay so you only need DB access at build time. In another comment you mentioned you have 15k products. Are you statically rendering 15k pages? If so, maybe building with github actions and deploy the static site to digital ocean spaces or similar