Run next info (available from version 12.0.8 and up)

/bin/sh: 1: pnpm: not found

    Operating System:
      Platform: linux
      Arch: x64
      Version: #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: 1.22.5
      pnpm: N/A
    Relevant packages:
      next: 12.0.11-canary.6
      react: 17.0.2
      react-dom: 17.0.2

What version of Next.js are you using?

12.0.11-canary.6

What version of Node.js are you using?

16.13.2

What browser are you using?

Firefox

What operating system are you using?

Ubuntu

How are you deploying your application?

next dev

Describe the Bug

When you have a page file which has a getStaticProps function exported, but no default export for a page component:

export const getStaticProps = async (context) => ({
    redirect: {
        destination: "https://example.com",
        permanent: false
    }
});

You get this server error:

Error: page /pageName getStaticProps can not be attached to a page's component and must be exported from the page. See more info here: https://nextjs.org/docs/messages/gssp-component-member

Even though the getStaticProps is correctly exported from the page.

Expected Behavior

Ideally having no page component export would be allowed and not cause an error (it's useful in cases where you'd only ever return a redirect or an error), but if this isn't supported the error message should say something like

Error: page /pageName does not have a default export page component. If the page won't ever render, export a function that returns null.

To Reproduce

1. Create a page that has a getStaticProps function but no default page component export, like the example in the "describe the bug" section
2. Run next dev
3. Navigate to the page in your browser