Getting obscure error during SSR after upgrading Next13 to Next14

[pdubb]

Summary

After upgrading Next from 13.5.6 to 14.2.20, we are getting the following error during SSR.

Internal error: Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

The browser shows a 500 error in the network tab, but once the client hydrates, everything renders as it should. Can someone offer any guidance as to why we're seeing this error?

We have a complex app that was working fine on the previous version, and as I try to diagnose the issues I can't seem to pinpoint any one particular import causing the problem. I've run circular dependency checks to see if that might be a cause, but there are no issues there.

Was something introduced in Next 14 that would cause something like this?

Additional information

No response

Example

No response

[mcollier]

@pdubb Did you ever figure this out?

[pdubb]

@mcollier It was a while ago, so I can't say what fixed it exactly, but we were able to get past it. If I recall, it required starting from scratch and updating one package at a time to see what kind of effect it had.