Andy Young

> guys, you can do it according to the following in packages.json. > > "installConfig": { "hoistingLimits": "workspaces" } thanks, it looks like that's a feature of yarn only -...

> I realise this feature as-implemented is "dangerous" PR now updated to support setting the env var `PATCH_PACKAGE_IGNORE_MISSING=1` so this can be set at deploy time (when some packages may...

I suspect this is due to Vercel's build process caching node_modules. (At least it was for me.) You can resolve by viewing the specific failing deployment within Vercel and selecting...

Update: issue created https://github.com/prisma/prisma/issues/14799 --- > I'm seeing a related issue which is that prisma inspects the database schema for a generated column I want it to not attempt to...

Simplified example supporting a foreign key that can refer to a related row from one of several different tables - in this example an identity that could be either a...

_Note to help any Prisma newcomers to this thread shortcut what I had to figure out:_ For Prisma v3+, the references to ``prisma.$executeRaw(`SET ... `)`` in examples above need tweaking...

> Might be asking a bit dumb here but what does `currentUser` refer to in the above examples? Where do you get that from if you want to add this...

FWIW I ended up not using Prisma Middleware and instead wrapping my prisma calls with a helper function to implement row-level security, given the need to wrap everything in transactions...

I am up and running successfully with a workaround/solution using Prisma Client Extensions that I posted under https://github.com/prisma/prisma/issues/20112 (which now I refer back, looks to be effectively a duplicate with...

I saw "basic sass support" was implemented in https://github.com/vercel/turbo/pull/4985 🙏 Perhaps this issue can now be updated or closed, @padmaia? > as soon as you https://github.com/import or https://github.com/extend etc in...