Jake Hopking

Yes - @AlessioGr I'm using Slate (as mentioned in the Adapters and Plugins section). @MarkAtOmniux - I've searched through my collections, and nowhere do I specify an `upload` or `relationship`...

I will try this. The more important question is what has changed between these two versions that could have caused this?

Nope - disabling all of these elements, I get the exact same error. Rolling back to `2.0.10` with fresh install again (`rm -rf node_modules` etc) all is good. Any other...

@jmikrut — James I'd love your thoughts here 🙏

> Did you also check for duplicate payload installs in your node modules? That's been happening more frequently recently Checked, and no duplicates here. > Hey @jakehopking I'm gonna jump...

Thanks for taking the time to look into this (and for fixing the type error you found). However I'm still completely stuck and confused how you managed to run my...

Reverting to `2.0.10` with again a completely fresh install in a fresh nvm env — all is working correctly again. This is driving me a little crazy 🤪 I notice...

Not so fast Jake... `yarn build` fails with this error: ```shell ❯ yarn build yarn run v1.22.21 $ cross-env NODE_ENV=production yarn clear:build && yarn build:payload && yarn build:server && yarn...

@DanRibbens **tldr;** - 🚀 Fixed everything by upgrading to `yarn 4.0.2` — `payload 2.3.0` now works for my solution. - `pnpm` created server side and Admin UI errors related to...

Thanks for your suggestions @AlessioGr. I will be sticking with `yarn 4` for now, but if I run into issues related to yarn in the future, I'll keep this in...