Tsemach Hadad

@paulpopus is there any incomplete PR ready to review ? , we are looking for example of custom component in Payload 3

@michael-ecb have you overcome this issue ?

@JessChowdhury We can try , just look at the code it can break easily It's not a big change anyway

The fix is very clear I can open a PR if needed

@JessChowdhury opened a PR for the fix:| https://github.com/payloadcms/payload/pull/8223

Closing the issue @PatrikKozak handled it as part of #7970

@jmikrut just opened a PR which just not logs the error , it's not resolving the next.js issue [https://github.com/payloadcms/payload/pull/8223](https://github.com/payloadcms/payload/pull/8223) But it can help us a lot to get cleaner logs

On beta 67 it can't run even if we add the deps: ` "@swc/cli": "0.3.12", "@swc/core": "1.4.14", "@swc/types": "0.1.10", ` In previous beta it ran this way now we get:...

Eventually on 67 I removed next 3 deps and all working o.k. now: `"@swc/cli": "0.3.12", "@swc/core": "1.4.14", "@swc/types": "0.1.10",` Apparently I added them in previous versions , now it causes...

Happens also to me on local storage and also on GCS storage so it's not related to S3 Look at [https://github.com/payloadcms/payload/pull/12622#issuecomment-2987818304](https://github.com/payloadcms/payload/pull/12622#issuecomment-2987818304) Same error occurs in other places