Prophet+ Debugger
SFCC debugger, uploader, log viewer and language tooling for Salesforce B2C Commerce Cloud sandboxes and staging.
Prophet+ is an open source fork of Prophet (MIT), maintained by TLG (The Level Group). It can be installed alongside the original Prophet — separate extension ID and settings namespace.
Highlights
- Status dashboard — problems first with a fix button (missing password, files not uploaded, code version mismatch…), then cards for connection, auto-upload, debugger and cartridge path with their actions
- Connection editor — every field of a connection in one page (hostname, Business Manager user, OCAPI, client certificate) with Test connection (DNS, credentials, certificate expiry, WebDAV, OCAPI)
- One status bar entry — connection, code version and upload state; tooltip with details and a click menu with the actions of the moment
- Upload Activity — every uploaded/deleted/failed file of the session with Retry, and per-cartridge progress of Upload All
- Log viewer — live tail of the sandbox logs (only new bytes are downloaded), filters by type, level and text, stack traces linked to your local files
- SFCC debugger from Prophet+ — start/stop without
launch.json, see where a thread is halted and jump there
- Overrides — hover a
require('*/…') / res.render() path to see every version in cartridge path order, open or compare them; Cartridge Path view with override counts and missing cartridges
- Controllers — routes with the chain SFRA runs (
post → replace → append), "Find Controller Route…" (Ctrl+F7)
- Two-factor upload — client certificate (
.p12/.pfx + passphrase) per connection for cert.staging.* hosts
- Secure by default — TLS certificates verified, passwords and secrets in the OS keychain
Supported features
- Upload cartridges and watch changes (auto-upload), Upload All, upload of a single file/cartridge from the explorer
- Script debugger (breakpoints, stepping, variables, watches, console)
- Sandbox log viewer (tail, filters, stack trace links) and log files view
- Syntax highlight for
isml and ds files
- Validate ISML files (htmlhint, configurable via
.htmlhintrc)
- Advanced ISML support (hover, autocomplete, formatting, symbols, rename tag, template/custom tag links)
- Go to definition for
require('*/…'), require('~/…'), module.superModule, res.render, Resource.msg, URLUtils.url
- Override CodeLens/hover, compare overrides, override template/script into another cartridge
- Cartridge path from the sandbox (OCAPI) or local settings
- Storefront Toolkit file open
- Sandbox file system (Impex, Temp, Realmdata, Static)
- SOAP WebService API download
- Import/export properties to/from CSV
- Multi-root workspaces
Warning: Some users have reported that the debugger can halt a sandbox. Ensure you can restart the sandbox before debugging.
Getting started
- Open a workspace that contains cartridges (folders with an SFCC
.project file).
- Open the Prophet+ icon in the activity bar → Add connection (or Import from dw.json).
- In the connection editor fill hostname and Business Manager user, press Test connection, then Save and activate.
- In the dashboard: Start auto-upload, Start debugger, choose the code version or the storefront site.
The extension detects cartridges via .project files — do not exclude .project in files.exclude.
Debugger
Start debugger in the dashboard (or Ctrl+Alt+P D) attaches to the active connection — no launch.json needed. Breakpoints, step and continue use VS Code's debug toolbar. A launch.json is still supported:
{
"version": "0.2.0",
"configurations": [
{ "type": "prophet-plus", "request": "launch", "name": "Attach to Sandbox" }
]
}
Optional launch field: trace — adapter diagnostic logging to the debug console (passwords are redacted).
Connections
Connections are managed in the connection editor. In settings they look like this (passwords, OCAPI secrets and certificate passphrases are never stored in settings, only in the OS keychain):
{
"extension.prophetPlus.userProfiles": [
{ "name": "me", "username": "user@company.com" }
],
"extension.prophetPlus.connections": [
{
"name": "Dev Sandbox",
"hostname": "dev01-realm-customer.demandware.net",
"userProfile": "me",
"clientId": "optional-ocapi-client-id"
},
{
"name": "Staging (two-factor)",
"hostname": "cert.staging.realm.customer.demandware.net",
"userProfile": "me",
"certificate": "/path/to/staging-client.p12"
}
]
}
- OCAPI (optional) — with Client ID + secret the cartridge path and the sites are read from the sandbox.
- Client certificate — for two-factor WebDAV hosts (
cert.staging.*). Certificates with the legacy RC2 encryption must be re-exported (openssl pkcs12 -legacy -in old.p12 -nodes -out cert.pem && openssl pkcs12 -export -in cert.pem -out new.p12); the error message explains it.
- Legacy
dw.json / dw.js is still supported when no connections exist, including "p12" and "passphrase":
{
"hostname": "example.demandware.net",
"username": "user",
"password": "password",
"code-version": "version2"
}
Upload
- Auto-upload — uploads changed files (dashboard Start/Pause,
Ctrl+Alt+P U)
- Upload All — full cartridge sync; files saved meanwhile are uploaded afterwards
- Upload Activity view — what was uploaded, failures with Retry
Key settings
| Setting |
Description |
extension.prophetPlus.upload.enabled |
Watch and upload changed files |
extension.prophetPlus.clean.on.start |
Full upload on startup (default: off) |
extension.prophetPlus.connections / userProfiles |
Connections and Business Manager users |
extension.prophetPlus.cartridges.path |
Local cartridge path fallback (: separated) |
extension.prophetPlus.statusBar.style |
compact (one entry, default) | detailed (separate entries) |
extension.prophetPlus.tls.rejectUnauthorized |
Verify TLS certificates (default true; user settings only) |
extension.prophetPlus.htmlhint.enabled |
ISML linting |
extension.prophetPlus.sandbox.filesystem.enabled |
Sandbox file system in the workspace |
Behind a TLS-intercepting corporate proxy, uploads use the OS certificate store; for the debugger on VS Code builds with Node < 22.15 set NODE_EXTRA_CA_CERTS or turn tls.rejectUnauthorized off.
jsconfig / types
Use a jsconfig.json per cartridge root and dw-api-types for richer IntelliSense.
Views
Open the Prophet+ activity bar for:
- Status — dashboard: problems, connection, auto-upload, debugger, cartridge path
- Upload Activity — uploads of the session, Retry, Upload All progress
- Controllers — routes with their SFRA chain
- Logs — sandbox log files (open them in the log viewer)
- Cartridge Path — cartridges in server order, override counts, missing cartridges
- Cartridges — workspace cartridge tree (optional)
Keyboard shortcuts
Ctrl+Alt+P followed by: C switch connection · U toggle auto-upload · O overrides of the current file · M sandbox actions · L log viewer · D start debugger / go to halted location · E connection editor. Ctrl+F7 finds a controller route.
SOAP WebService API
Right-click a WSDL file → Download SOAP Web Service API…
Requires javadoc on your PATH (same as UX Studio).
Support
Questions, bug reports and feature requests: GitHub Issues.
When reporting a bug, include the VS Code version, the Prophet+ version and the relevant output of the Prophet+ output channel — remove hostnames, usernames and any other data of your sandbox first.
For the upstream Prophet project, see SqrTT/prophet.
Development
Requirements: Node.js 20+ and VS Code 1.85+. Every GitHub Release also has the .vsix attached, for manual installation (Extensions: Install from VSIX…).
git clone https://github.com/accountstlg/prophet-plus.git
cd prophet-plus
npm install
npm run compile # development build (npm run watch to rebuild on change)
npm test # unit tests
npm run test:integration # integration tests (mock sandbox, no real instance needed)
npm run package # builds prophet-plus-<version>.vsix
Press F5 in VS Code to launch an Extension Development Host with the extension loaded.
Contributing
Pull requests are welcome. Please:
- open an issue first for larger changes;
- keep
npm run verify green (unit tests, production build, integration tests) — CI runs it on every pull request;
- describe user-visible changes under
## [Unreleased] in CHANGELOG.md and leave the version in package.json alone: it is bumped when a release is cut;
- never commit credentials,
dw.json files, hostnames or log excerpts of real instances.
npm run hooks:install enables the git hooks in .githooks: they reject commits that add credential files, real instance hostnames or issue-tracker IDs in commit messages, plus any pattern you list in .githooks/blocklist.local (not versioned — see blocklist.local.example).
License
MIT — see LICENSE.txt.
Original Prophet contributors