NextJS Imports | Default oder Named?

[LarsFlieger]

Sure... it's true that the docs don't explicitly say this... but let me ask you something. How else would the framework know what to import? I mean, if you export some page called MySuperCoolPage, how does Next.js know to import that specifically? Default exports don't have this problem, since they don't have a name.

Source: https://stackoverflow.com/questions/74281609/is-it-possible-to-use-only-named-exports-in-a-nextjs-project#comment131142592_74281609

Im Router Level geht leider kein Named Export da der Router über den default import den Component erkennt.

Ich würde aber vorschlagen trotzdem im Code Named Exports zu nutzen (Vorteile: Explicit over implicit, better UX while developing, easier refactoring....) und nur die Router Components werden über default exportiert.

Also

• Da wo geht named exports (Components) export const Example = ...
• Da wo nicht geht default exports (Router) const Example = ...; export default Example

[LarsFlieger]

Interesting is that you can exports function like this:

export default function FirstPost() {
    return <h1>First Post</h1>;
}