メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| 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.
Diagnose and fix headless login issues on VTEX storefronts — covering authorized domain setup and simulating an authenticated session by copying VtexIdclientAutCookie cookies.
Use when debugging what crawlers or bots see on a deco site, verifying if SSR is active for bots, or diagnosing firstByteThresholdMS behavior.
Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.
Configure deco.cx Variants — the mechanism that swaps the value of a section, page, image, message, or ANY custom-typed prop based on a matcher rule (device, cookie, date, A/B test, geo, path, query string, etc.). Use when the user asks to A/B test a section, personalize a page per audience/segment, show different banners per device or location, schedule a promotion by date/cron, add a new variant-able type (promotion, VTEX segment, product list, menu items), write a custom matcher, or generally wire up `website/flags/multivariate*` in `.deco/blocks/*.json`. Covers the JSON shape (`variants: [{ value, rule }]`), the resolution order (first match wins, catch-all last), every built-in matcher (`always`, `never`, `device`, `date`, `cron`, `random`, `cookie`, `host`, `pathname`, `queryString`, `userAgent`, `location`, `site`, `environment`, `multi`, `negate`), how to compose them with `multi` (and/or) and `negate`, the 8-line boilerplate to create your own `flags/multivariate/<type>.ts`, the shape of a custom `ma
Install and configure the Blog Manager on a deco-site storefront. Covers the blog app, page routes, sections, Blog Manager MCP connection in Studio, and first-run brand context initialization.
Use when inside a deco.cx ecommerce repository (deco.ts present, decobot in PR history) and the user wants automated QA for purchase-journey correctness — set up E2E coverage, test the add-to-cart / checkout flow, or scaffold a CI gate for the store with the @decocms/qa engine. NOT for load/cache performance testing (use deco-e2e-testing) or hand-written Playwright spec files.