/
githubmirror
/
next.js
Обзор
Документация
Войти
/
githubmirror
/
next.js
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
canary
errors/no-typos.mdx
55 строк
1 KB
Mukunda Rao Katta
docs: add documentation for no-typos ESLint rule (#92809)
16 апр 2026, 01:31
Не верифицирован
16 апр 2026, 01:31
219c0bc
Код
Авторство
О чём код?
--- title: No Typos --- > Prevent common typos in Next.js data fetching functions. ## Why This Error Occurred A near-miss spelling of a Next.js data fetching function was detected. This rule checks for typos in these exports inside the `pages/` directory: - `getStaticProps` - `getStaticPaths` - `getServerSideProps` When the name is off by even a single character, Next.js will not recognize the export and your data fetching logic will silently not run. ## Possible Ways to Fix It Check the spelling and casing of your exported function so it matches a Next.js data fetching function exactly. **Before:** ```jsx filename="pages/index.js" // Typo: "getStaticProp" instead of "getStaticProps" export async function getStaticProp() { return { props: {}, } } ``` **After:** ```jsx filename="pages/index.js" export async function getStaticProps() { return { props: {}, } } ``` Casing also matters — a single wrong-case letter will trip the rule: ```jsx filename="pages/index.js" // Typo: lowercase "p" in "props" export async function getServerSideprops() { return { props: {} } } ``` ## Useful Links - [`getStaticProps`](/docs/pages/building-your-application/data-fetching/get-static-props) - [`getStaticPaths`](/docs/pages/building-your-application/data-fetching/get-static-paths) - [`getServerSideProps`](/docs/pages/building-your-application/data-fetching/get-server-side-props)