b0de69b1d9
The root cause of the schema mismatch was skipIfSchemaCurrent=true in TinaCMS's syncProject() call, which caused TinaCloud to skip re-indexing when it thought the schema SHA hadn't changed. This left TinaCloud with a stale GraphQL schema missing the pages collection (PagesSeo type). Fix: add an explicit curl step before the build that calls TinaCloud's reset endpoint WITHOUT skipIfSchemaCurrent, forcing a full re-index. Keep --skip-cloud-checks in the build command to avoid the circular dependency (build failing because TinaCloud is still indexing). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
42 lines
1.3 KiB
JSON
42 lines
1.3 KiB
JSON
{
|
|
"name": "project-init",
|
|
"private": true,
|
|
"version": "0.0.0",
|
|
"type": "module",
|
|
"scripts": {
|
|
"dev": "tinacms dev -c \"vite\"",
|
|
"build": "tinacms build --skip-cloud-checks && node scripts/sync-blog.mjs && node scripts/copy-pages.mjs && node scripts/generate-sitemap.mjs && tsc -b && vite build && node scripts/prerender.mjs",
|
|
"lint": "eslint .",
|
|
"preview": "vite preview",
|
|
"sync-blog": "node scripts/sync-blog.mjs",
|
|
"deploy": "bash scripts/deploy.sh"
|
|
},
|
|
"dependencies": {
|
|
"@amplitude/unified": "^1.0.2",
|
|
"framer-motion": "^12.34.0",
|
|
"mixpanel-browser": "^2.75.0",
|
|
"react": "^19.2.0",
|
|
"react-dom": "^19.2.0",
|
|
"react-helmet-async": "^3.0.0",
|
|
"react-intersection-observer": "^10.0.2",
|
|
"react-router-dom": "^7.13.1",
|
|
"tinacms": "^3.6.1"
|
|
},
|
|
"devDependencies": {
|
|
"@eslint/js": "^9.39.1",
|
|
"@tinacms/cli": "^2.1.9",
|
|
"@types/node": "^24.10.1",
|
|
"@types/react": "^19.2.7",
|
|
"@types/react-dom": "^19.2.3",
|
|
"@vitejs/plugin-react": "^5.1.1",
|
|
"eslint": "^9.39.1",
|
|
"eslint-plugin-react-hooks": "^7.0.1",
|
|
"eslint-plugin-react-refresh": "^0.4.24",
|
|
"globals": "^16.5.0",
|
|
"mime-types": "^2.1.35",
|
|
"puppeteer": "^24.0.0",
|
|
"typescript": "~5.9.3",
|
|
"typescript-eslint": "^8.48.0",
|
|
"vite": "^7.3.1"
|
|
}
|
|
}
|