vercel/next.js / errors / no-typos.mdx

---

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:

// Typo: "getStaticProp" instead of "getStaticProps"
export async function getStaticProp() {
  return {
    props: {},
  }
}

After:

export async function getStaticProps() {
  return {
    props: {},
  }
}

Casing also matters — a single wrong-case letter will trip the rule:

// Typo: lowercase "p" in "props"
export async function getServerSideprops() {
  return { props: {} }
}

Useful Links

• getStaticProps
• getStaticPaths
• getServerSideProps