export-all-in-page.mdx


title: Re-exporting all exports from a page is disallowed

Why This Error Occurred

The following export can potentially break Next.js' compilation of pages:

export * from '...'

This is because Node.js code may be leaked to the browser build, causing an error. For example, the following two pages:

import fs from 'fs'

export default function A() {
  return <main />
}

export function getStaticProps() {
  fs
  return { props: {} }
}
export * from './example-a'

Would cause the following error:

Module not found: Can't resolve 'fs' in './pages/example-b.js'

Possible Ways to Fix It

Update your page to re-export the default component only:

export { default } from './example-b'

If the other page uses getServerSideProps or getStaticProps, you can re-export those individually too:

export { default, getServerSideProps } from './example-b'
// or
export { default, getStaticProps } from './example-b'
// or
export { default, getStaticProps, getStaticPaths } from './example-b/[dynamic]'

Rendered from the public repository vercel/next.js on GitHub; content belongs to its authors. Cached for up to an hour.

errors/export-all-in-page.mdx · vercel/next.js | Docs MD