We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no-default-exports
Our style guide enforces import/no-default-export. We find this helps with TypeScript IntelliSense (auto-completion) in IDEs like VSCode.
import/no-default-export
Right now, Next.js requires default exports in pages and API routes.
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 () { /* .. */ }
We could, as an alternative, disable this rule for anything in the pages directory (and in any other places it would be needed).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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:
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).
The text was updated successfully, but these errors were encountered: