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
43 lines
1023 B
JSON
43 lines
1023 B
JSON
{
|
|
"name": "@autumn/website",
|
|
"version": "0.1.0",
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next dev -p 3004",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"lint": "eslint"
|
|
},
|
|
"dependencies": {
|
|
"@gsap/react": "^2.1.2",
|
|
"@mdx-js/loader": "^3.1.1",
|
|
"@mdx-js/mdx": "^3.1.1",
|
|
"@mdx-js/react": "^3.1.1",
|
|
"@next/mdx": "^16.2.4",
|
|
"@types/react": "^19.2.14",
|
|
"@vercel/analytics": "^2.0.1",
|
|
"framer-motion": "^12.38.0",
|
|
"gray-matter": "^4.0.3",
|
|
"gsap": "^3.15.0",
|
|
"lottie-react": "^2.4.1",
|
|
"lottie-web": "^5.13.0",
|
|
"matter-js": "^0.20.0",
|
|
"motion": "^12.38.0",
|
|
"next": "16.2.4",
|
|
"ngrok": "^5.0.0-beta.2",
|
|
"react": "19.2.4",
|
|
"react-dom": "19.2.4",
|
|
"react-syntax-highlighter": "^16.1.1",
|
|
"remark-frontmatter": "^5.0.0"
|
|
},
|
|
"devDependencies": {
|
|
"@tailwindcss/postcss": "^4.2.2",
|
|
"@tailwindcss/typography": "^0.5.19",
|
|
"@types/react-syntax-highlighter": "^15.5.13",
|
|
"eslint": "^10.2.0",
|
|
"eslint-config-next": "16.2.1",
|
|
"tailwindcss": "^4.2.2",
|
|
"typescript": "^6.0.2"
|
|
}
|
|
}
|