AppNext.js uses the App component to initialize pages. You can override it and control the page initialization. Which allows you to do amazing things like:
componentDidCatchTo override the default App, create the file ./pages/_app.js as shown below:
// import App from 'next/app'\n\nfunction MyApp({ Component, pageProps }) {\n return <Component {...pageProps} />\n}\n\n// Only uncomment this method if you have blocking data requirements for\n// every single page in your application. This disables the ability to\n// perform automatic static optimization, causing every page in your app to\n// be server-side rendered.\n//\n// MyApp.getInitialProps = async (appContext) => {\n// // calls page's `getInitialProps` and fills `appProps.pageProps`\n// const appProps = await App.getInitialProps(appContext);\n//\n// return { ...appProps }\n// }\n\nexport default MyApp\nThe Component prop is the active page, so whenever you navigate between routes, Component will change to the new page. Therefore, any props you send to Component will be received by the page.
pageProps is an object with the initial props that were preloaded for your page, it's an empty object if the page is not using getInitialProps.
\n\nAdding a custom
\ngetInitialPropsin yourAppwill disable Automatic Static Optimization.
If you’re using TypeScript, take a look at our TypeScript documentation.
\nFor more information on what to do next, we recommend the following sections:
\n\n"},"__N_SSG":true}