I ran npm update, verified the new version was installed, but package.json still showed the old version. That sent me down a rabbit hole trying to understand how npm actually manages versions.

The irony of debugging Velite watch mode: I restored code that was intentionally removed to fix double builds. Here's what happened.

Velite's draft filtering wasn't working in production. Here's what I tried, why it failed, and what finally fixed it.

I wanted to hide draft posts in production. Thought I could just add draft: true to frontmatter. Turns out Velite needs explicit schema definition AND filtering logic.

Added @tailwindcss/typography to fix bullet points. It worked, but suddenly headings and code blocks looked terrible. Here's why plugins aren't always the answer.

I wanted to add syntax highlighting to my Velite/Next.js blog using Shiki. Seemed straightforward - install packages, configure, done. Wrong. Here's what went wrong and how I fixed it.

Spent hours debugging Velite with Next.js 16 - wrong imports, watch mode not working with Turbopack, async params, and more.