Pages Router + getInitialProps = Static worker unexpectedly #55817

DenysMoro · 2023-09-22T12:28:51Z

Link to the code that reproduces this issue

https://github.com/ifier/next-js-SIGINT

To Reproduce

Don't start app
Run npm run build
See list of errors

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
...

If you will go to _app and comment out getInitialProps section fully - it will build with no errors.

Current vs. Expected behavior

I would expect not to see this list

Verify canary release

I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.5.2
      eslint-config-next: 13.5.2
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

No response

The text was updated successfully, but these errors were encountered:

pbrissaud · 2023-09-24T23:24:04Z

Same error after upgrade Next.js from v13.4.19 to v13.5.2and using a trpc backend :

function App({ Component, pageProps }: AppProps) {
  return (
    <>
      <style jsx global>
        {`
          :root {
            --lora-font: ${lora.style.fontFamily};
          }
        `}
      </style>
      <ThemeProvider attribute="class">
        <UserProvider>
          <Toaster />
          <Component {...pageProps} />
        </UserProvider>
      </ThemeProvider>
      <ReactQueryDevtools initialIsOpen={false} />
      <Script
        src={`https://maps.googleapis.com/maps/api/js?key=${process.env.NEXT_PUBLIC_GOOGLE_MAPS_API_KEY}&libraries=places&callback=Function.prototype`}
      />
    </>
  );
}

export default trpc.withTRPC(App);

yobottehg · 2023-09-25T12:54:57Z

Same here but without getInitialProps in_app.tsx but with initialProps related code in _error.tsx:

Pages router and SSR only (ServerSideProps everywhere)

Error.getInitialProps = ({ res, err }: NextPageContext) => {
  const statusCode = res ? res.statusCode : err ? err.statusCode : 404
  return { statusCode }
}

export default Error

 npm run build

> ksb-website@1.0.0 build
> NODE_ENV=production next build

   Skipping validation of types
   Skipping linting
 ✓ Creating an optimized production build   
 ✓ Compiled successfully
 ✓ Collecting page data   
 ✓ Finalizing page optimization   

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT

Removing Error.getInitialProps removes the error.

This is 100% from the docs:
https://nextjs.org/docs/pages/building-your-application/routing/custom-error#more-advanced-error-page-customizing

longzheng · 2023-09-26T11:29:37Z

Same here but without getInitialProps in_app.tsx but with initialProps related code in _error.tsx:

Pages router and SSR only (ServerSideProps everywhere)

Error.getInitialProps = ({ res, err }: NextPageContext) => {
  const statusCode = res ? res.statusCode : err ? err.statusCode : 404
  return { statusCode }
}

export default Error

 npm run build

> ksb-website@1.0.0 build
> NODE_ENV=production next build

   Skipping validation of types
   Skipping linting
 ✓ Creating an optimized production build   
 ✓ Compiled successfully
 ✓ Collecting page data   
 ✓ Finalizing page optimization   

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT

Removing Error.getInitialProps removes the error.

This is 100% from the docs: https://nextjs.org/docs/pages/building-your-application/routing/custom-error#more-advanced-error-page-customizing

Good find. I'm also running this on a project that uses a custom getInitialProps for Sentry error reporting as recommended by Next.js' example code and documentation

next.js/examples/with-sentry/pages/_error.tsx

Lines 21 to 28 in ed6e801

 CustomErrorComponent.getInitialProps = async (contextData) => { 

 // In case this is running in a serverless function, await this in order to give Sentry 

 // time to send the error before the lambda exits 

 await Sentry.captureUnderscoreErrorException(contextData) 

 // This will contain the status code of the response 

 return NextErrorComponent.getInitialProps(contextData) 

 }

mick-feller · 2023-10-02T20:53:02Z

i have the same issue, seems to be introduced in 13.5, 13.4 seems to be working fine for me.

evanwinter · 2023-10-04T15:53:26Z

I am seeing this is 13.4.12, so not sure if 13.5 is the only culprit

oliviertassinari · 2023-10-08T18:09:59Z

Same error after upgrade Next.js from v13.4.19 to v13.5.2

I have also noticed how all the content of the <Head> element used in a page is no longer in the static export. e.g.

yarn build && yarn next export && npx serve out

import Head from 'next/head'
import { Inter } from 'next/font/google'
import styles from '@/styles/Home.module.css'

const inter = Inter({ subsets: ['latin'] })

export default function Home() {
  return (
    <>
      <Head>
        <title>Create Next App</title>
        <meta name="description" content="Generated by create next app" />
        <meta name="viewport" content="width=device-width, initial-scale=1" />
        <link rel="icon" href="/favicon.ico" />
      </Head>

Gone

If I do:

diff --git a/src/pages/index.tsx b/src/pages/index.tsx
index 27c489b..b98b0c1 100644
--- a/src/pages/index.tsx
+++ b/src/pages/index.tsx
     </>
   )
 }
+
+Home.getInitialProps = () => ({});

A reproduction:

Open https://github.com/oliviertassinari/next-55817
Run yarn && yarn build && yarn next export && npx serve out
v13.4.19 work OK, v13.5.1 is KO.

salmanorak · 2023-10-09T12:00:50Z

I have gone through a couple of versions. I have run the build with all the below versions.
The first version that doesn't throw errors is 13.3.4. All version I have tried above 13.3.4 was throwing SIGINT or SIGTERM error on the build logs.

Version tried:

13.4.0
13.4.19
13.5.2
13.5.3
13.5.4

I want to share these results in case it can be helpful.

ADTC · 2023-10-18T05:22:30Z

Referencing here, a comment with my findings: #48192 (reply in thread)

Rakhymbek · 2024-07-02T12:48:47Z

Same here but without getInitialProps in_app.tsx but with initialProps related code in _error.tsx:
Pages router and SSR only (ServerSideProps everywhere)
Error.getInitialProps = ({ res, err }: NextPageContext) => {
  const statusCode = res ? res.statusCode : err ? err.statusCode : 404
  return { statusCode }
}

export default Error
 npm run build

> ksb-website@1.0.0 build
> NODE_ENV=production next build

   Skipping validation of types
   Skipping linting
 ✓ Creating an optimized production build   
 ✓ Compiled successfully
 ✓ Collecting page data   
 ✓ Finalizing page optimization   

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Removing Error.getInitialProps removes the error.
This is 100% from the docs: https://nextjs.org/docs/pages/building-your-application/routing/custom-error#more-advanced-error-page-customizing
Good find. I'm also running this on a project that uses a custom getInitialProps for Sentry error reporting as recommended by Next.js' example code and documentation

next.js/examples/with-sentry/pages/_error.tsx

Lines 21 to 28 in ed6e801

CustomErrorComponent.getInitialProps = async (contextData) => {

// In case this is running in a serverless function, await this in order to give Sentry

// time to send the error before the lambda exits

await Sentry.captureUnderscoreErrorException(contextData)

// This will contain the status code of the response

return NextErrorComponent.getInitialProps(contextData)

}

Did you solve it by removing CustomErrorComponent.getInitialProps?
I have the same configuration in _error.tsx from Sentry cli.
What did you do exactly?

Rakhymbek · 2024-07-02T12:55:51Z

Same here but without getInitialProps in_app.tsx but with initialProps related code in _error.tsx:

Pages router and SSR only (ServerSideProps everywhere)

Error.getInitialProps = ({ res, err }: NextPageContext) => {
  const statusCode = res ? res.statusCode : err ? err.statusCode : 404
  return { statusCode }
}

export default Error

 npm run build

> ksb-website@1.0.0 build
> NODE_ENV=production next build

   Skipping validation of types
   Skipping linting
 ✓ Creating an optimized production build   
 ✓ Compiled successfully
 ✓ Collecting page data   
 ✓ Finalizing page optimization   

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT

Removing Error.getInitialProps removes the error.

This is 100% from the docs: https://nextjs.org/docs/pages/building-your-application/routing/custom-error#more-advanced-error-page-customizing

Same here but without getInitialProps in_app.tsx but with initialProps related code in _error.tsx:

Pages router and SSR only (ServerSideProps everywhere)

Error.getInitialProps = ({ res, err }: NextPageContext) => {
  const statusCode = res ? res.statusCode : err ? err.statusCode : 404
  return { statusCode }
}

export default Error

 npm run build

> ksb-website@1.0.0 build
> NODE_ENV=production next build

   Skipping validation of types
   Skipping linting
 ✓ Creating an optimized production build   
 ✓ Compiled successfully
 ✓ Collecting page data   
 ✓ Finalizing page optimization   

Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT
Static worker unexpectedly exited with code: null and signal: SIGINT

Removing Error.getInitialProps removes the error.

This is 100% from the docs: https://nextjs.org/docs/pages/building-your-application/routing/custom-error#more-advanced-error-page-customizing

You've just removed Error. getInitialProps, but did you add something to replace it?

DenysMoro added the bug Issue was opened via the bug report template. label Sep 22, 2023

oliviertassinari mentioned this issue Oct 8, 2023

Bump dependencies mui/toolpad#2743

Merged

1 task

This was referenced Nov 25, 2023

Bump next to ^13.5.6 - autoclosed mui/mui-x#10539

Closed

Bump next to 13.4.19 mui/material-ui#38559

Merged

oliviertassinari mentioned this issue Feb 13, 2024

[docs-infra] Fix <title> generation mui/mui-x#11182

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Pages Router + getInitialProps = Static worker unexpectedly #55817

Pages Router + getInitialProps = Static worker unexpectedly #55817

DenysMoro commented Sep 22, 2023

pbrissaud commented Sep 24, 2023

yobottehg commented Sep 25, 2023 •

edited

Loading

longzheng commented Sep 26, 2023 •

edited

Loading

mick-feller commented Oct 2, 2023

evanwinter commented Oct 4, 2023

oliviertassinari commented Oct 8, 2023 •

edited

Loading

salmanorak commented Oct 9, 2023 •

edited

Loading

ADTC commented Oct 18, 2023

Rakhymbek commented Jul 2, 2024 •

edited

Loading

Rakhymbek commented Jul 2, 2024

Pages Router + getInitialProps = Static worker unexpectedly #55817

Pages Router + getInitialProps = Static worker unexpectedly #55817

Comments

DenysMoro commented Sep 22, 2023

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Verify canary release

Provide environment information

Which area(s) are affected? (Select all that apply)

Additional context

pbrissaud commented Sep 24, 2023

yobottehg commented Sep 25, 2023 • edited Loading

longzheng commented Sep 26, 2023 • edited Loading

mick-feller commented Oct 2, 2023

evanwinter commented Oct 4, 2023

oliviertassinari commented Oct 8, 2023 • edited Loading

salmanorak commented Oct 9, 2023 • edited Loading

ADTC commented Oct 18, 2023

Rakhymbek commented Jul 2, 2024 • edited Loading

Rakhymbek commented Jul 2, 2024

yobottehg commented Sep 25, 2023 •

edited

Loading

longzheng commented Sep 26, 2023 •

edited

Loading

oliviertassinari commented Oct 8, 2023 •

edited

Loading

salmanorak commented Oct 9, 2023 •

edited

Loading

Rakhymbek commented Jul 2, 2024 •

edited

Loading