菜单
Update deco and apps dependencies in a deco.cx storefront. Use when the user asks to bump, update, or upgrade deco, apps, or storefront dependencies.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/decocms/storefront-skills --skill bump-dependencies命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Create a new page on a deco.cx storefront — including route, metadata, sections, and dynamic route params (e.g. /category/:slug). Use when the user asks to add, create, or scaffold a new page or route in a deco site, or to pass a URL param into a section/loader.
Understand and configure image optimization in deco.cx storefronts — components, quality settings, bypass rules, platform-specific handling, CDN proxy, and format negotiation. Use when the user asks about images, image quality, image optimization, or image components.
Understand and configure video in deco.cx storefronts — the Video component, autoplay, and especially audio/sound. Use when the user asks about video, video sound, audio, "video with no sound", "video is silent", "how to unmute", muted, autoplay, or how to enable sound on an uploaded video.
| name | bump-dependencies |
| description | Update deco and apps dependencies in a deco.cx storefront. Use when the user asks to bump, update, or upgrade deco, apps, or storefront dependencies. |
Deco storefronts pin their dependencies in deno.json. The two main packages to keep updated are @deco/deco (the core framework) and apps (the deco apps ecosystem).
deno task updateThe recommended way to bump dependencies:
deno task update
This runs Deco's official update script (https://deco.cx/update) which automatically updates all deco-related dependencies to their latest compatible versions.
After updating, clean the cache to avoid stale modules:
deno task cache_clean
Which runs rm deno.lock; deno cache -r main.ts.
deno.jsonWhen you need to pin a specific version or update selectively, edit deno.json directly.
There are two groups of entries per package — JSR imports and CDN imports — and their versions must stay in sync.
// deno.json → imports
{
// JSR import — main entry point
"@deco/deco": "jsr:@deco/deco@1.191.2",
"@deco/deco/": "jsr:@deco/deco@1.191.2/",
// CDN import — used for raw file access
"deco/": "https://cdn.jsdelivr.net/gh/deco-cx/deco@1.191.2/",
// Dev tools — keep in sync with deco version
"@deco/dev": "jsr:@deco/dev@1.191.2",
"@deco/dev/": "jsr:@deco/dev@1.191.2/"
}
When bumping @deco/deco, update all four entries to the same version. Also update @deco/dev to match.
// deno.json → imports
{
// CDN import — main entry point
"apps/": "https://cdn.jsdelivr.net/gh/deco-cx/apps@0.144.1/"
}
Single entry — just update the version number in the URL.
Before bumping, check the latest available versions:
https://jsr.io/@deco/decohttps://github.com/deco-cx/apps/releasesOr from the command line:
# Latest @deco/deco on JSR
deno info jsr:@deco/deco
# Latest apps release on GitHub
gh release list -R deco-cx/apps -L 1
deno.json under imports@deco/decorm deno.lock; deno cache -r main.ts
deno task start
deno task check
These are secondary packages that may also need updating, but less frequently:
| Package | Import pattern | Notes |
|---|---|---|
@deco/mcp | jsr:@deco/mcp@x.y.z | MCP server integration |
@deco/durable | jsr:@deco/durable@x.y.z | Durable objects |
@deco/warp | jsr:@deco/warp@x.y.z | Edge runtime |
These do not necessarily follow the same version as @deco/deco. Update them independently as needed.
If you see import errors or stale modules after updating:
rm deno.lock; deno cache -r main.ts
Run the full check suite to catch issues early:
deno task check
This runs formatting, linting, and type checking.
If @deco/deco JSR version and deco/ CDN version don't match, you'll get runtime errors or inconsistent behavior. Always keep them in sync.