cdc1c2bade
next-mdx-remote evaluates MDX at runtime with a different React version than Next.js 16's internal canary, causing build failures. Switch to @next/mdx which compiles MDX through Next.js's own bundler pipeline. - Replace next-mdx-remote with @next/mdx, @mdx-js/mdx, @mdx-js/loader - Use dynamic imports for blog MDX files instead of MDXRemote - Add remark-frontmatter so compiler skips YAML frontmatter blocks - Gate cache/CSP headers to production only (immutable dev chunks were poisoning browser cache) Made-with: Cursor
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.js. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.