Support no-default-exports workflows

[mrmckeb]

Describe the feature you'd like to request

Our style guide enforces import/no-default-export. We find this helps with TypeScript IntelliSense (auto-completion) in IDEs like VSCode.

Right now, Next.js requires default exports in pages and API routes.

Describe the solution you'd like

Where Next.js expects default exports today, we'd like the option of using named exports.

For example:

// pages/my-page.tsx

export function Page ()  { /* .. */ }

export async function getServerSideProps () { /* .. */ }

Describe alternatives you've considered

We could, as an alternative, disable this rule for anything in the pages directory (and in any other places it would be needed).

[lfades]

TypeScript does a good job with default exports when the default export is named, I think having this rule enabled forces you to never use a default export 🤔

[mrmckeb]

I think having this rule enabled forces you to never use a default export

Correct, which is our preferred approach - for consistency.

[advaitju]

Beyond consistency and avoiding divergent names for default exports, I'd also like to reduce the import bloat and pollution in Intellisense. Layouts and pages will rarely if ever be imported anyway.

The ideal solution imo would be if there was a named export in page.js or layout.js that was a reserved word for Next, e.g. export function Page() { ... } or export function Layout() { ... }