No Typos

A data-fetching function export in a Pages Router page file contains a typo. Next.js recognizes only getStaticProps, getServerSideProps, and getStaticPaths by exact name. A misspelling such as getStatcProps is silently ignored at runtime, causing the page to behave as if static with no data. This lint rule catches those mistakes at development time.

References

nextjs.org/docs/messages/no-typos

In this namespace

← previous no-title-in-document-head No Title in Document Head next → no-unwanted-polyfillio No Unwanted Polyfill.io

no-html-link-for-pages no-img-element no-page-custom-font no-sync-scripts no-title-in-document-head no-typos no-unwanted-polyfillio react-hydration-error server-only-in-client-component sharp-missing-in-production