next.js: Page.tsx with default and named export fails on build (esLint)
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 22.1.0: Sun Oct 9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
Binaries:
Node: 18.14.0
npm: 9.3.1
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 13.4.14-canary.2
eslint-config-next: 13.4.13
react: 18.2.0
react-dom: 18.2.0
typescript: 5.1.6
Next.js Config:
output: N/A
Which area(s) of Next.js are affected? (leave empty if unsure)
App Router, ESLint (eslint-config-next), TypeScript (plugin, built-in types)
Link to the code that reproduces this issue or a replay of the bug
N/a
To Reproduce
Create a page.tsx file in the app dir with a default export for the page, and a named export to represent any util function.
export default function Page() {
return (
// page return
)
}
export function utilHelper(){
return (
// function return
)
}
Describe the Bug
Previously I have been able to have named exports in addition to a default export in my page.tsx files. All of a sudden the above configuration of a page.tsx file now fails on build with the error:
“Type error: Page “pathtopage/page.tsx” does not match the required types of a Next.js Page. “utilHelper” is not a valid Page export field.”
As far as the current build of the site running on vercel suggests, and as the docs state, one should be able to export in this way from any file, including page.tsx.
Expected Behavior
no erros when exporting a named function with a default export from a file
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
vercel
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 17
- Comments: 15 (1 by maintainers)
I’m so close to losing my sh*t with Nextjs
If this is really the reason, and not a technical requirement, I would strongly encourage that this requirement is removed.
It is not ‘best practices’ that is literally just an opinion. An equally valid opinion is to prefer locality of behavior, which this rule impairs. React itself pushed back against ‘best practices’ when it was built, and now think of components as concerns, not technologies. Locality of behavior underlies this concept.
You may disagree, but it’s all opinions.
If this export restriction is not a technical requirement, I would prefer to see this error removed.
same situation. I fixed by using
export default function xxxinstead ofexport default const xxxBased on the issues you’re encountering with Next.js during your build process, it seems you’re running into a common problem with Next.js’s stricter validation of page exports in version 14. This validation aims to ensure that page files only export React components that are intended to be used as pages, not utility functions or other named exports. You need to tackle this with a precise refactor to align with best practices and address the compilation errors effectively
Understanding the Issue Next.js expects that files under the pages directory (or any file treated as a page component) should only default export a React component that corresponds to a page. If you have other named exports, it can cause the build to fail as Next.js might interpret them as potential page candidates which they are not.
Solution: Restructure Exports and Component Organization To resolve this issue, we need to separate utility functions or non-page components from the page files, ensuring that only the default page export is present in page component files. Here’s how you can adjust your setup:
Separate Utility Functions and Shared Components: Move any named exports that are not page components into separate files within a suitable directory, such as components or utils. Adjust Imports in the Main Page File: Update import statements in your main page files to reflect these changes.
Hello. Also experiencing this. Is there any update? Thanks
Would love to see an option to disable or configure this TypeScript plugin feature. My use case: In order to make it easier to render the interface portion of async server components in tests and Storybook, I would like to follow a pattern like below, but this is prevented by this named export issue:
Example test that this pattern would support:
Example Storybook story:
Related #56832, #50870