BuildWithMatija
  1. Home
  3. Blog
  5. Sanity
  7. Fix NEXT_PUBLIC_SANITY_DATASET Error in Sanity CLI

Fix NEXT_PUBLIC_SANITY_DATASET Error in Sanity CLI

Load .env in sanity.cli.ts and add env.ts fallbacks to stop NEXT_PUBLIC_SANITY_DATASET errors running npx sanity dev

22nd November 2025·Updated on:12th November 2025··
Sanity

📋 Complete Sanity Development Guides

Get practical Sanity guides with working examples, schema templates, and time-saving prompts. Everything you need to build faster with Sanity CMS.

No spam. Unsubscribe anytime.

📄View markdown version
0

Frequently Asked Questions

About the author

Matija Žiberna

Matija Žiberna

Full-stack developer, co-founder

AboutResume

Self-taught full-stack developer sharing lessons from building software and startups.

I'm Matija Žiberna, a self-taught full-stack developer and co-founder passionate about building products, writing clean code, and figuring out how to turn ideas into businesses. I write about web development with Next.js, lessons from entrepreneurship, and the journey of learning by doing. My goal is to provide value through code—whether it's through tools, content, or real-world software.

Contents

  • The Root Cause
  • Fix #1: Load dotenv in sanity.cli.ts
  • Fix #2: Use Fallback Values in env.ts
  • Why Both Fixes Matter
On this page:
  • The Root Cause
  • Fix #1: Load dotenv in sanity.cli.ts
  • Fix #2: Use Fallback Values in env.ts
  • Why Both Fixes Matter
Build with Matija logo

Build with Matija

Modern websites, content systems, and AI workflows built for long-term growth.

Services

  • Headless CMS Websites
  • Next.js & Headless CMS Advisory
  • AI Systems & Automation
  • Website & Content Audit

Resources

  • Case Studies
  • How I Work
  • Blog
  • Topics
  • CMS Hub
  • E-commerce Hub
  • B2B Website Strategy
  • Dashboard

Headless CMS

  • Payload CMS Developer
  • CMS Migration
  • Multi-Tenant CMS
  • Payload vs Sanity
  • Payload vs WordPress
  • Payload vs Contentful

Get in Touch

Ready to modernize your stack? Let's talk about what you're building.

Book a discovery callContact me →
© 2026Build with Matija•All rights reserved•Privacy Policy•Terms of Service
BuildWithMatija
Get In Touch

I was setting up Sanity Studio for a project when I ran npx sanity dev and got hit with an error: "Missing environment variable: NEXT_PUBLIC_SANITY_DATASET". The frustrating part? The variable was clearly defined in my .env file. After digging into it, I realized the issue happens in two places. Here's exactly how to fix it.

The Root Cause

When you run npx sanity dev, the Sanity CLI doesn't automatically load your .env file like Next.js does. Additionally, client-side components that import from your env.ts file can't access environment variables the same way server-side code can. The browser can't read .env files directly.

Fix #1: Load dotenv in sanity.cli.ts

Your Sanity CLI configuration file needs to explicitly load environment variables. Open sanity.cli.ts and add the dotenv import at the top:

typescript
// File: sanity.cli.ts
import { defineCliConfig } from 'sanity/cli'
import 'dotenv/config'

const projectId = process.env.NEXT_PUBLIC_SANITY_PROJECT_ID
const dataset = process.env.NEXT_PUBLIC_SANITY_DATASET

export default defineCliConfig({ api: { projectId, dataset }, studioHost: "your-studio-host" })

The import 'dotenv/config' line tells Node.js to load your .env file before anything else runs. This ensures the environment variables are available when the CLI initializes.

Fix #2: Use Fallback Values in env.ts

The second issue is in your src/lib/sanity/env.ts file. If client-side components import from this file and the environment variables aren't available in the browser context, you'll get an error. Instead of throwing an error with assertValue(), provide sensible defaults:

typescript
// File: src/lib/sanity/env.ts
export const apiVersion =
  process.env.NEXT_PUBLIC_SANITY_API_VERSION || '2024-12-27'

export const dataset = process.env.NEXT_PUBLIC_SANITY_DATASET || 'production'

export const projectId = process.env.NEXT_PUBLIC_SANITY_PROJECT_ID || 'ytvlzq9e'

This way, if the environment variables are available (injected by Next.js at build time), they get used. If not, the fallback values keep your client-side components working without throwing errors.

Why Both Fixes Matter

The CLI fix ensures the Sanity CLI commands have access to your project configuration. The fallback values ensure that client-side code (like custom Sanity Studio components) doesn't crash when environment variables aren't directly accessible in the browser.

Now when you run npx sanity dev, it'll load your environment variables correctly, and your client-side components will work without errors.

Let me know in the comments if you hit any other environment variable issues with Sanity, and subscribe for more practical development guides.

Thanks, Matija