[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79743W53FS2HC9PRDJAKCS7":3,"skill-same:01M79743W53FS2HC9PRDJAKCS7":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M79743W53FS2HC9PRDJAKCS7","vercel-upgrade-migration",null,"Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection.\nUse when upgrading Vercel CLI versions, migrating Node.js runtimes,\nor updating Next.js between major versions on Vercel.\nTrigger with phrases like \"upgrade vercel\", \"vercel migration\",\n\"vercel breaking changes\", \"update vercel CLI\", \"next.js upgrade on vercel\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-upgrade-migration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-upgrade-migration\ndescription: |\n  Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection.\n  Use when upgrading Vercel CLI versions, migrating Node.js runtimes,\n  or updating Next.js between major versions on Vercel.\n  Trigger with phrases like \"upgrade vercel\", \"vercel migration\",\n  \"vercel breaking changes\", \"update vercel CLI\", \"next.js upgrade on vercel\".\nallowed-tools: Read, Write, Edit, Bash(vercel:*), Bash(npm:*), Bash(npx:*), Bash(git:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, migration, upgrade]\n---\n# Vercel Upgrade Migration\n\n## Overview\nSafely upgrade Vercel CLI, Node.js runtime versions, and framework versions (especially Next.js) on Vercel. Covers breaking change detection, vercel.json schema changes, and rollback strategy.\n\n## Current State\n!`vercel --version 2>\u002Fdev\u002Fnull || echo 'Vercel CLI not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA'`\n!`cat package.json 2>\u002Fdev\u002Fnull | jq -r '.dependencies.next \u002F\u002F \"no next.js\"' 2>\u002Fdev\u002Fnull || echo 'N\u002FA'`\n\n## Prerequisites\n- Current Vercel CLI installed\n- Git for version control\n- Test suite available\n- Preview deployment for testing\n\n## Instructions\n\n### Step 1: Check Current Versions\n```bash\n# Current CLI version\nvercel --version\n\n# Current Node.js runtime on Vercel\ncat package.json | jq '.engines.node'\n# Or check vercel.json\ncat vercel.json | jq '.functions'\n\n# Check for available CLI updates\nnpm outdated -g vercel\n\n# Check framework version\nnpm ls next react\n```\n\n### Step 2: Upgrade Vercel CLI\n```bash\n# Upgrade to latest\nnpm install -g vercel@latest\n\n# Or specific version\nnpm install -g vercel@39\n\n# Verify\nvercel --version\n```\n\n**CLI breaking changes to watch for:**\n- v28+: `vercel env pull` output format changed\n- v32+: `vercel dev` uses new function runtime\n- v37+: `vercel.json` `builds` property deprecated in favor of framework detection\n\n### Step 3: Upgrade Node.js Runtime\n```json\n\u002F\u002F package.json — specify the Node.js version\n{\n  \"engines\": {\n    \"node\": \"20.x\"\n  }\n}\n```\n\nAvailable runtimes on Vercel:\n| Runtime | Status | EOL |\n|---------|--------|-----|\n| Node.js 18.x | Supported | April 2025 |\n| Node.js 20.x | Active LTS (recommended) | April 2026 |\n| Node.js 22.x | Current | October 2027 |\n\n```bash\n# Test locally with the target Node version first\nnvm use 20\nnpm test\nnpm run build\n```\n\n### Step 4: Upgrade Next.js on Vercel\n```bash\n# Use the Next.js upgrade codemod\nnpx @next\u002Fcodemod@latest upgrade\n\n# Or manual upgrade\nnpm install next@latest react@latest react-dom@latest\n\n# Check for breaking changes\nnpx @next\u002Fcodemod --dry-run\n```\n\n**Key Next.js migration points:**\n- **13 → 14**: App Router stable, Turbopack available, Server Actions stable\n- **14 → 15**: `fetch` no longer cached by default, `cookies()` is async, `NextRequest.geo` removed (use `geolocation()` from `@vercel\u002Ffunctions`)\n- **vercel.json changes**: `rewrites`\u002F`redirects` in `next.config.js` take precedence over `vercel.json`\n\n### Step 5: Test in Preview Before Production\n```bash\n# Create a branch for the upgrade\ngit checkout -b upgrade\u002Fvercel-cli-39\n\n# Make changes and push\ngit add -A && git commit -m \"chore: upgrade vercel CLI and Node.js 20\"\ngit push -u origin upgrade\u002Fvercel-cli-39\n\n# Vercel auto-deploys a preview — test it\nvercel ls | head -3\ncurl -s https:\u002F\u002Fmy-app-git-upgrade-vercel-cli-39-team.vercel.app\u002Fapi\u002Fhealth\n\n# Run full test suite against preview\nnpm test -- --env=preview\n```\n\n### Step 6: Rollback Strategy\n```bash\n# If the upgrade breaks production — instant rollback\nvercel rollback\n\n# Pin to a specific CLI version in CI\n# .github\u002Fworkflows\u002Fdeploy.yml\n# - run: npm install -g vercel@38  # pin to known good version\n\n# Revert Node.js runtime\n# Change engines.node back in package.json\n# Push and redeploy\n```\n\n## vercel.json Schema Migration\n\nDeprecated `builds` property (v2 → current):\n```json\n\u002F\u002F Old (deprecated):\n{\n  \"builds\": [\n    { \"src\": \"api\u002F**\u002F*.ts\", \"use\": \"@vercel\u002Fnode\" }\n  ]\n}\n\n\u002F\u002F New (framework auto-detection):\n{\n  \"functions\": {\n    \"api\u002F**\u002F*.ts\": {\n      \"runtime\": \"nodejs20.x\",\n      \"maxDuration\": 30\n    }\n  }\n}\n```\n\n## Output\n- Vercel CLI upgraded to latest version\n- Node.js runtime version updated in package.json\n- Framework upgraded with codemods applied\n- Preview deployment tested before production promotion\n- Rollback strategy documented\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `Build failed` after Node upgrade | Dependency incompatible with new Node | Check `npm ls` for native modules, rebuild |\n| `Module not found` after Next.js upgrade | Import paths changed | Run `npx @next\u002Fcodemod` for automatic fixes |\n| `vercel.json` validation error | Schema changed in new CLI version | Remove deprecated `builds`, use `functions` |\n| `FUNCTION_INVOCATION_FAILED` | Runtime API removed in new Node.js | Check Node.js changelog for removed APIs |\n| Preview works but prod fails | Env vars differ between environments | Verify production env vars match preview |\n\n## Resources\n- [Vercel CLI Changelog](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel\u002Freleases)\n- [Node.js Runtime on Vercel](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fnode-js)\n- [Next.js Upgrade Guide](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fbuilding-your-application\u002Fupgrading)\n- [vercel.json Reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fproject-configuration)\n\n## Next Steps\nFor CI\u002FCD integration, see `vercel-ci-integration`.\n","# Vercel Upgrade Migration\n\n## Overview\nSafely upgrade Vercel CLI, Node.js runtime versions, and framework versions (especially Next.js) on Vercel. Covers breaking change detection, vercel.json schema changes, and rollback strategy.\n\n## Current State\n!`vercel --version 2>\u002Fdev\u002Fnull || echo 'Vercel CLI not installed'`\n!`node --version 2>\u002Fdev\u002Fnull || echo 'N\u002FA'`\n!`cat package.json 2>\u002Fdev\u002Fnull | jq -r '.dependencies.next \u002F\u002F \"no next.js\"' 2>\u002Fdev\u002Fnull || echo 'N\u002FA'`\n\n## Prerequisites\n- Current Vercel CLI installed\n- Git for version control\n- Test suite available\n- Preview deployment for testing\n\n## Instructions\n\n### Step 1: Check Current Versions\n```bash\n# Current CLI version\nvercel --version\n\n# Current Node.js runtime on Vercel\ncat package.json | jq '.engines.node'\n# Or check vercel.json\ncat vercel.json | jq '.functions'\n\n# Check for available CLI updates\nnpm outdated -g vercel\n\n# Check framework version\nnpm ls next react\n```\n\n### Step 2: Upgrade Vercel CLI\n```bash\n# Upgrade to latest\nnpm install -g vercel@latest\n\n# Or specific version\nnpm install -g vercel@39\n\n# Verify\nvercel --version\n```\n\n**CLI breaking changes to watch for:**\n- v28+: `vercel env pull` output format changed\n- v32+: `vercel dev` uses new function runtime\n- v37+: `vercel.json` `builds` property deprecated in favor of framework detection\n\n### Step 3: Upgrade Node.js Runtime\n```json\n\u002F\u002F package.json — specify the Node.js version\n{\n  \"engines\": {\n    \"node\": \"20.x\"\n  }\n}\n```\n\nAvailable runtimes on Vercel:\n| Runtime | Status | EOL |\n|---------|--------|-----|\n| Node.js 18.x | Supported | April 2025 |\n| Node.js 20.x | Active LTS (recommended) | April 2026 |\n| Node.js 22.x | Current | October 2027 |\n\n```bash\n# Test locally with the target Node version first\nnvm use 20\nnpm test\nnpm run build\n```\n\n### Step 4: Upgrade Next.js on Vercel\n```bash\n# Use the Next.js upgrade codemod\nnpx @next\u002Fcodemod@latest upgrade\n\n# Or manual upgrade\nnpm install next@latest react@latest react-dom@latest\n\n# Check for breaking changes\nnpx @next\u002Fcodemod --dry-run\n```\n\n**Key Next.js migration points:**\n- **13 → 14**: App Router stable, Turbopack available, Server Actions stable\n- **14 → 15**: `fetch` no longer cached by default, `cookies()` is async, `NextRequest.geo` removed (use `geolocation()` from `@vercel\u002Ffunctions`)\n- **vercel.json changes**: `rewrites`\u002F`redirects` in `next.config.js` take precedence over `vercel.json`\n\n### Step 5: Test in Preview Before Production\n```bash\n# Create a branch for the upgrade\ngit checkout -b upgrade\u002Fvercel-cli-39\n\n# Make changes and push\ngit add -A && git commit -m \"chore: upgrade vercel CLI and Node.js 20\"\ngit push -u origin upgrade\u002Fvercel-cli-39\n\n# Vercel auto-deploys a preview — test it\nvercel ls | head -3\ncurl -s https:\u002F\u002Fmy-app-git-upgrade-vercel-cli-39-team.vercel.app\u002Fapi\u002Fhealth\n\n# Run full test suite against preview\nnpm test -- --env=preview\n```\n\n### Step 6: Rollback Strategy\n```bash\n# If the upgrade breaks production — instant rollback\nvercel rollback\n\n# Pin to a specific CLI version in CI\n# .github\u002Fworkflows\u002Fdeploy.yml\n# - run: npm install -g vercel@38  # pin to known good version\n\n# Revert Node.js runtime\n# Change engines.node back in package.json\n# Push and redeploy\n```\n\n## vercel.json Schema Migration\n\nDeprecated `builds` property (v2 → current):\n```json\n\u002F\u002F Old (deprecated):\n{\n  \"builds\": [\n    { \"src\": \"api\u002F**\u002F*.ts\", \"use\": \"@vercel\u002Fnode\" }\n  ]\n}\n\n\u002F\u002F New (framework auto-detection):\n{\n  \"functions\": {\n    \"api\u002F**\u002F*.ts\": {\n      \"runtime\": \"nodejs20.x\",\n      \"maxDuration\": 30\n    }\n  }\n}\n```\n\n## Output\n- Vercel CLI upgraded to latest version\n- Node.js runtime version updated in package.json\n- Framework upgraded with codemods applied\n- Preview deployment tested before production promotion\n- Rollback strategy documented\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `Build failed` after Node upgrade | Dependency incompatible with new Node | Check `npm ls` for native modules, rebuild |\n| `Module not found` after Next.js upgrade | Import paths changed | Run `npx @next\u002Fcodemod` for automatic fixes |\n| `vercel.json` validation error | Schema changed in new CLI version | Remove deprecated `builds`, use `functions` |\n| `FUNCTION_INVOCATION_FAILED` | Runtime API removed in new Node.js | Check Node.js changelog for removed APIs |\n| Preview works but prod fails | Env vars differ between environments | Verify production env vars match preview |\n\n## Resources\n- [Vercel CLI Changelog](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel\u002Freleases)\n- [Node.js Runtime on Vercel](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fnode-js)\n- [Next.js Upgrade Guide](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fbuilding-your-application\u002Fupgrading)\n- [vercel.json Reference](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fproject-configuration)\n\n## Next Steps\nFor CI\u002FCD integration, see `vercel-ci-integration`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","vercel","migration","upgrade","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection.\nUse when upgrading Vercel CLI versions, migrating Node.js runtimes,\nor updating Next.js between major versions on Vercel.\nTrigger with phrases like \"upgrade vercel\", \"vercel migration\",\n\"vercel breaking changes\", \"update vercel CLI\", \"next.js upgrade on vercel\".\n","Read, Write, Edit, Bash(vercel:*), Bash(npm:*), Bash(npx:*), Bash(git:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-upgrade-migration",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill vercel-upgrade-migration",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-upgrade-migration",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-upgrade-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-upgrade-migration\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]