nextjs-monorepo-example VS prerender

For info you can have a look to a setup in httpx (simple yarn 4 + workspaces) or nextjs-monorepo-example (yarn 4 workspaces + turbo + recipe for docker)

I like https://github.com/belgattitude/nextjs-monorepo-example/

It's pretty easy to setup renovate, the "update dependency XXX PR" comes with the upstream changelogs from which you can have an idea of the work to do if needed. Compared to some other similar tools: monorepo support (ie: workspace:"") + possibility to dedupe your lock file + an easy way to regroug packages (ie: "@vitest/ui" and "vitest" together). An example: https://github.com/belgattitude/nextjs-monorepo-example/blob/main/renovate.json5.

https://github.com/belgattitude/nextjs-monorepo-example Here is a very good example monorepo with a similiar usecase

Until the “flat” eslint config file becomes the standard, Here’s a nice example of how to do it.

PS: You can see there: https://github.com/belgattitude/nextjs-monorepo-example (bunch of recipes but definitely needs a cleanup) and this question https://github.com/belgattitude/nextjs-monorepo-example/discussions/2220

There is one moderately complex example monorepo that includes a Next.js project and shared lib projects here: https://github.com/belgattitude/nextjs-monorepo-example

I sometimes put some examples in https://github.com/belgattitude/nextjs-monorepo-example. It's bare-bone and offer few pros/cons (no nx, no turbo.., but you can upgrade along the way).

But if you have time, you can have a look to this https://github.com/belgattitude/nextjs-monorepo-example/blob/main/apps/web-app/src/features/demo/demo.config.ts.

- If you're using yarn 1, go yarn 3+ with "node_linker: node_modules", eventually "nmMode: hardlinks-local" and yarn workspace plugin (example of .yarnrc.yml config). You'll get some speed up and the update should not be too long to do. Note: this gives comparable speed of pnpm in my experience (whatever benchmark I read).

So then just to experiment, I set up https://github.com/prerender/prerender on my own VPS in like an hour... and done & dusted... no more effort needed to think about SSR issues anymore. Seems great, and I can't figure out why it's not more popular.

Spending like 1 hour setting up prerender on my server is much preferable to the ongoing issues that come with having to make all my code work with SSR frameworks. And there's the added bonus that my servers don't need to waste resources doing SSR for regular human users.

Here’s an alternative that I use: https://prerender.io and GH is https://github.com/prerender/prerender

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/92.0.4512.0 Safari/537.36 Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/91.0.4472.114 Safari/537.36 Prerender (+https://github.com/prerender/prerender) ...

Ah, I didn't realize this wasn't solved -- a quick search turns up:

- https://github.com/WICG/webcomponents/issues/788

- https://github.com/w3c/DOM-Parsing/issues/58

- https://github.com/w3ctag/design-reviews/issues/494

- https://web.dev/declarative-shadow-dom

In pre-render they seem to have started in this direction extremely recently:

https://github.com/prerender/prerender/pull/731/files

I don't use prerender so I can't definitively speak to it being solved and hiccup-free, but I think that limitation is going to go away in the future.

Using something like: https://github.com/prerender/prerender

Have you used prerender - https://github.com/prerender/prerender ? Seems to be doing the same thing.