B2C DX VS Code Extension v1.0.6

Download the .vsix file below and install via:

code --install-extension b2c-vs-extension-1.0.6.vsix

Or in VS Code: Extensions → ⋯ → Install from VSIX...

Changelog

Patch Changes

• Updated dependencies [94c7ba9]:
  • @salesforce/b2c-tooling-sdk@1.21.3

Agent skills plugin artifacts for b2c-agent-plugins v1.7.0. Download the *-skills.zip files below.

See the Agent Skills & Plugins guide for installation and usage.

Changelog

Minor Changes

• #603 94c7ba9 - Add Codex plugin packaging for the B2C DX MCP server so Codex CLI and Codex in the ChatGPT desktop app can install and load the MCP server directly through the B2C Developer Tooling plugin marketplace. Claude Code marketplace installation remains supported by the same plugin. (Thanks @clavery!)

Patch Changes

• #603 94c7ba9 - Fix skill installation output so mixed-source downloads do not show an unresolved version placeholder, repair the b2c-hooks skill frontmatter, and identify the affected skill path in future parsing warnings. (Thanks @clavery!)

• #601 332f0a4 - Correct B2C agent skill examples to use supported Script APIs, hook extension points, OCAPI contracts, and schema-valid metadata. Generated implementations no longer rely on nonexistent APIs or invalid request and response shapes. (Thanks @dkatashev!)

@salesforce/b2c-cli@1.21.4

Patch Changes

• #603 94c7ba9 - Fix skill installation output so mixed-source downloads do not show an unresolved version placeholder, repair the b2c-hooks skill frontmatter, and identify the affected skill path in future parsing warnings. (Thanks @clavery!)

• Updated dependencies [94c7ba9]:

  • @salesforce/b2c-tooling-sdk@1.21.3

@salesforce/b2c-dx-mcp@1.9.3

Patch Changes

• Updated dependencies [94c7ba9]:
  • @salesforce/b2c-tooling-sdk@1.21.3

@salesforce/b2c-tooling-sdk@1.21.3

Patch Changes

• #603 94c7ba9 - Fix skill installation output so mixed-source downloads do not show an unresolved version placeholder, repair the b2c-hooks skill frontmatter, and identify the affected skill path in future parsing warnings. (Thanks @clavery!)

b2c-vs-extension@1.0.6

Patch Changes

• Updated dependencies [94c7ba9]:
  • @salesforce/b2c-tooling-sdk@1.21.3

Documentation

Patch Changes

• #603 94c7ba9 - Add Codex plugin packaging for the B2C DX MCP server so Codex CLI and Codex in the ChatGPT desktop app can install and load the MCP server directly through the B2C Developer Tooling plugin marketplace. Claude Code marketplace installation remains supported by the same plugin. (Thanks @clavery!)

Agent Skills Plugins

Minor Changes

• #603 94c7ba9 - Add Codex plugin packaging for the B2C DX MCP server so Codex CLI and Codex in the ChatGPT desktop app can install and load the MCP server directly through the B2C Developer Tooling plugin marketplace. Claude Code marketplace installation remains supported by the same plugin. (Thanks @clavery!)

Patch Changes

• #603 94c7ba9 - Fix skill installation output so mixed-source downloads do not show an unresolved version placeholder, repair the b2c-hooks skill frontmatter, and identify the affected skill path in future parsing warnings. (Thanks @clavery!)

• #601 332f0a4 - Correct B2C agent skill examples to use supported Script APIs, hook extension points, OCAPI contracts, and schema-valid metadata. Generated implementations no longer rely on nonexistent APIs or invalid request and response shapes. (Thanks @dkatashev!)

B2C DX VS Code Extension v1.0.5

Download the .vsix file below and install via:

code --install-extension b2c-vs-extension-1.0.5.vsix

Or in VS Code: Extensions → ⋯ → Install from VSIX...

Changelog

Patch Changes

• #598 258f6bd - Stop the VS Code extension from blocking other extensions in empty or non-B2C windows. Because the extension registers a TypeScript server plugin, VS Code activates it whenever any JavaScript/TypeScript file is opened — including windows with no folder. In that case the extension no longer falls back to the process working directory, and all cartridge/workspace discovery now runs only from a concrete workspace folder and never from a home or filesystem-root directory, so it can't trigger a recursive filesystem scan that stalls the extension host. (Thanks @clavery!)

B2C DX VS Code Extension v1.0.4

Download the .vsix file below and install via:

code --install-extension b2c-vs-extension-1.0.4.vsix

Or in VS Code: Extensions → ⋯ → Install from VSIX...

Changelog

Patch Changes

• #592 f6b4ced - Detect nested dw.json project roots in VS Code workspaces and allow nested folders to be pinned from Explorer, so parent-folder and multi-root layouts connect to the intended project. (Thanks @clavery!)

• #592 f6b4ced - Treat activation of an already-active code version as success, preserve useful OCAPI fault details, and avoid redundant activation choices in VS Code. (Thanks @clavery!)

• Updated dependencies [f6b4ced]:

  • @salesforce/b2c-tooling-sdk@1.21.2

Agent skills plugin artifacts for b2c-agent-plugins v1.6.2. Download the *-skills.zip files below.

See the Agent Skills & Plugins guide for installation and usage.

Changelog

Patch Changes

• #588 3a7843d - Document the sf-toolkit="off" attribute on <isinclude> in the b2c-isml skill, explaining how to disable Storefront Toolkit markers and when to use it. (Thanks @clavery!)

• #577 fe264a7 - Document the order hook lifecycle in the b2c-hooks skill: the beforePOST → afterPOST → modifyPOSTResponse sequence, Status.ERROR rollback semantics per phase, the two-hook pattern for persisting a failed order while returning an HTTP error, and request.custom for inter-hook data passing. (Thanks @charithaT07!)

@salesforce/b2c-cli@1.21.3

Patch Changes

• #596 a5fbe3f - Fix slas client update corrupting existing callback URIs. When merging with the current client, the command split the API's pipe-delimited callbackUri value on commas instead of pipes, so the entire list was sent back as a single string and the update was rejected with "CallbackURI must be a valid URL". Callback URIs are now parsed with the same shared helper used for redirect URIs everywhere in the SLAS commands, so the two paths can no longer disagree. (Thanks @clavery!)

@salesforce/b2c-cli@1.21.2

Patch Changes

• #592 f6b4ced - Treat activation of an already-active code version as success, preserve useful OCAPI fault details, and avoid redundant activation choices in VS Code. (Thanks @clavery!)

• Updated dependencies [f6b4ced]:

  • @salesforce/b2c-tooling-sdk@1.21.2

@salesforce/b2c-dx-mcp@1.9.2

Patch Changes

• Updated dependencies [f6b4ced]:
  • @salesforce/b2c-tooling-sdk@1.21.2

@salesforce/b2c-tooling-sdk@1.21.2

Patch Changes

• #592 f6b4ced - Treat activation of an already-active code version as success, preserve useful OCAPI fault details, and avoid redundant activation choices in VS Code. (Thanks @clavery!)

b2c-vs-extension@1.0.4

Patch Changes

• #592 f6b4ced - Detect nested dw.json project roots in VS Code workspaces and allow nested folders to be pinned from Explorer, so parent-folder and multi-root layouts connect to the intended project. (Thanks @clavery!)

• #592 f6b4ced - Treat activation of an already-active code version as success, preserve useful OCAPI fault details, and avoid redundant activation choices in VS Code. (Thanks @clavery!)

• Updated dependencies [f6b4ced]:

  • @salesforce/b2c-tooling-sdk@1.21.2

Documentation

Patch Changes

• #592 f6b4ced - Detect nested dw.json project roots in VS Code workspaces and allow nested folders to be pinned from Explorer, so parent-folder and multi-root layouts connect to the intended project. (Thanks @clavery!)

• #590 3fb0871 - Document the figma-to-sfnext-pagedesigner plugin in the Agent Skills guide (Thanks @lukejohnson-sf!)

• #592 f6b4ced - Treat activation of an already-active code version as success, preserve useful OCAPI fault details, and avoid redundant activation choices in VS Code. (Thanks @clavery!)

Agent Skills Plugins

Patch Changes

• #588 3a7843d - Document the sf-toolkit="off" attribute on <isinclude> in the b2c-isml skill, explaining how to disable Storefront Toolkit markers and when to use it. (Thanks @clavery!)

• #577 fe264a7 - Document the order hook lifecycle in the b2c-hooks skill: the beforePOST → afterPOST → modifyPOSTResponse sequence, Status.ERROR rollback semantics per phase, the two-hook pattern for persisting a failed order while returning an HTTP error, and request.custom for inter-hook data passing. (Thanks @charithaT07!)

B2C DX VS Code Extension v1.0.3

Download the .vsix file below and install via:

code --install-extension b2c-vs-extension-1.0.3.vsix

Or in VS Code: Extensions → ⋯ → Install from VSIX...

Changelog

Patch Changes

• Updated dependencies [1fe5ff2]:
  • @salesforce/b2c-tooling-sdk@1.21.1

Agent skills plugin artifacts for b2c-agent-plugins v1.6.0. Download the *-skills.zip files below.

See the Agent Skills & Plugins guide for installation and usage.

Changelog

Minor Changes

• #589 886a33e - Add the figma-to-sfnext-pagedesigner plugin: an agent skill that converts a Figma frame into live Storefront Next Page Designer blocks — splitting the frame into one block per section, reconciling brand tokens, generating React + Tailwind components with Page Designer decorator metadata and SCAPI product loaders, and validating design fidelity. Requires the Figma MCP server. Install with claude plugin install figma-to-sfnext-pagedesigner@b2c-developer-tooling. (Thanks @lukejohnson-sf!)

Patch Changes

• #583 e9c5659 - The b2c-logs skill now documents custom-category log file discovery. It explains that a custom logger category writes to its own custom-<prefix>-*.log file (distinct from customerror), that the prefix is the first argument to Logger.getLogger(prefix, category), and how to find and read these files with logs list --filter custom and logs get --filter custom-<prefix>, plus the webdav ls --root logs fallback. This makes the retrieval skill self-contained for triaging integration and job logs, which almost always use a custom category. (Thanks @charithaT07!)

• #581 1fe5ff2 - Expose directly related documentation IDs from Salesforce Help child-topic links and Developer Center guide TOCs, including articles previously omitted from composite Help maps or hyphenated topic filenames. CLI and MCP documentation search results can now be paged by ranked position, so agents can traverse the full published content without surfacing future-profiled Help content. (Thanks @clavery!)