examples VS nextjs-monorepo-example

Is anyone aware of a way to make a direct connection to Postgres with transaction support on Vercel Edge functions? The 'pg' package doesn't work on edge for me. The obvious answer would be @vercel/postgres but I find their lack of documentation rough and for whatever reason I can't get it to connect on my local computer using the Supabase-provided local database connection string. This is apparently a known issue (https://github.com/vercel/storage/issues/123, https://github.com/vercel/examples/issues/701) where in order to make this (or neon's package) work you need a WebSocket proxy? Is a direct Postgres connection from edge just impossible right now? Or do others have it working somehow?

I have cloned this repo: https://github.com/vercel/examples/tree/main/python/nextjs-flask. I am using the repo to make an api call from the front end to the back end. when running fetch("/api") I get an error with status 500, why is that?

Demo: Alt Text Generator GitHub: Alt Text Generator Repository

I copied the Template that they provide for the testing, you can get the template source on GitHub. I modified its page.tsx file just to set and get a value from the database.

Take a look at this example: https://github.com/vercel/examples/tree/main/solutions/subdomain-auth

So AFAIK now with Vercel Postgres is possible to have connection pooling using prisma out of the box, this means that no more bottlenecks with lots of clients connected to the web app right? Source: https://github.com/vercel/examples/blob/main/storage/postgres-prisma/prisma/schema.prisma

I have a server component that reads a database table in this new way (Vercel Next JS Postgres Example). I also have a client component that updates that calls a fetch to update the same table. How can I ensure that the data in my server component doesn't grow stale?

Additionally, Redis can be used in combination with Vercel Edge cache using: https://github.com/vercel/examples/tree/main/edge-api-routes/cache-control

Hostname rewrites example

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).