Netlify build error with sanity-nextjs-landing-pages starter

I can see you're running into build errors with the sanity-nextjs-landing-pages starter on Netlify. Build errors with older Sanity starters are unfortunately quite common, typically due to dependency conflicts and outdated packages that don't play well with current build environments.

Troubleshooting your current setup

If you want to continue with this specific template, the Netlify build error is likely caused by:

• Outdated dependencies - Older Next.js versions or Sanity packages that conflict with current build environments
• Node.js version mismatch - Netlify might be using a different Node version than the template expects
• ESLint configuration issues - Common with older templates using deprecated ESLint configs

You can try setting the Node.js version explicitly in Netlify by adding a .nvmrc file to your repo or setting the NODE_VERSION environment variable in your Netlify dashboard.

Consider using current templates instead

Rather than debugging an older template, I'd recommend starting with one of Sanity's actively maintained starters. According to the official Sanity templates page, there are over 100 official templates and 1,200+ community templates available, including:

• 382 Next.js templates specifically designed for modern Next.js + Sanity projects
• 334 marketing site templates if you're building landing pages
• Templates with built-in support for features like collaborative editing, localization, and optimization

You can browse all available templates at sanity.io/templates and filter by framework, use case, and features.

Why modern templates matter

Starting with a current template means:

• Dependencies are compatible with modern build platforms like Netlify
• You get access to newer Sanity features like Content Releases and the Live Content API
• Active community support and regular updates
• Better performance and developer experience

If you need specific help with the exact error message you're seeing, sharing the full error output in the Sanity Slack community would help folks provide more targeted debugging advice!