Riley Langbein comments

Results 41 comments of


                                            Riley Langbein

afterChange Hook Only Executes for the Active Locale When Publishing Changes Across Multiple Locales

@JarrodMFlesch could you please elaborate on the reasoning behind the teams decision?

Adding a custom upload component to the edit view does not work

@JarrodMFlesch tagging you as requested.

Adding a custom upload component to the edit view does not work

Hoping we can get eyes on this soon, it's blocking me from releasing a payload plugin I've created. I've put together a PR that seems to resolve it for me,...

Adding a custom upload component to the edit view does not work

Just giving this one a friendly bump, hoping we can get the attached PR merged into the next release.

feat(db-postgres): optionally allow to store blocks as JSON and add support for "in" operator within richText

> When can we expect this PR? This feature is really useful when there are around 50 blocks in one collection. Right now, I'm using a workaround that works great,...

feat(db-postgres): optionally allow to store blocks as JSON and add support for "in" operator within richText

@maximseshuk this is impressive! Thanks so much for sharing. I'll try this out on my end and see how it goes. Edit: unfortunately after trying a number of different things...

`beforeValidate` hook runs, but doesn't update UI during `update` operation

I've gone back and determined it started occurring in beta 128.

Turbopack HMR - Error: Could not find the module X in the React Client Manifest (Next.js 15.5.0 and 16.0.1)

I'm running into this as well. Also just want to say this is a great write-up, a very informative github issue, appreciate the effort put into it.

Error: Payload does not support using Turbopack for production builds (Version 3.64.0 -> 3.65.0)

If you need access to `turbopack build` and are not concerned with the bundle size regression, you can do a `pnpm patch` and implement the changes that were reverted in...

`findByID()` returns incorrect results compared to equivalent `find()`

It looks like the tests pass if both `createdAt: true` and `updatedAt: true` are included in `select`. I do agree this seems like a bug.