Christoph Bratschi

Fails here: https://github.com/payloadcms/payload/blob/48f1299fcba3e3811c6a7f31499f238537f9a5e3/packages/payload/src/uploads/getFileByURL.ts#L1

Patched the transpiled getFileByURL.js file: ```JS "use strict"; Object.defineProperty(exports, "__esModule", { value: true }); Object.defineProperty(exports, "default", { enumerable: true, get: function() { return _default; } }); //const _nodefetch = /*#__PURE__*/...

See discussion here: https://github.com/node-fetch/node-fetch/issues/1279#issuecomment-1275933370

I checked the latest Payload version and there is still an issue left: the getExternalFile() call is silently failing: https://github.com/payloadcms/payload/blob/8015e999cd5834f532a200ef03fd392d04b3209f/packages/payload/src/uploads/generateFileData.ts#L76 I modified the code to get the thrown exception: ```...

Could you please re-open this issue? This is still reproducible.

Could you please re-open and patch according to my description below. ### Error Handling First log the error on console like on this line in the same file: https://github.com/payloadcms/payload/blob/b974a2c042a1b4c58ca9a740d5be7f16bf66177f/packages/payload/src/uploads/generateFileData.ts#L256 Then...

@denolfe Still the same. The only change is that the error is now better handled and its message is shown in a toast. Here is the full error message: ```...

I have this issue in all my routes, once in Swiper and once in a OIDC client component. This happened since upgrading to 14.1 and all attempts to workaround it...

Adding this to package.json finally solved this issue. Deleted node_modules/.cache and .next folders. During the first run there where many errors but after that the app runs again. ``` "browserslist":...

We load the translation in server component code and pass it to a provider which is a client component. Because the error page is a client component we cannot use...