Skip to content

v0.4.32

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jun 02:26
· 19 commits to master since this release
v0.4.32
18ddd78

Changelog

[0.4.32] — 2026

Fixed

  • The Debug Launcher no longer shows an empty panel after selecting org/space/folder — When cf-sync had synced the org/space structure but not yet the space's apps (or stored spaces in the legacy string format), the launcher served the empty topology list as-is: a READY screen with zero app rows and no live fetch — reported by users as "the Debug Launcher is completely blank". An empty topology app list is now treated as no data on both the webview and extension side, falling through to the cached/live cf apps fetch.
  • Webview render failures are visible and recoverable instead of a blank/frozen panel — A renderer exception used to leave the panel blank (on first render) or frozen on a stale screen, with no diagnostics. The launcher now has a render error boundary that shows a recovery screen with a "Reload Launcher" button, reports the error (with stack) to the CDS Debug output channel via a new WEBVIEW_ERROR message, forwards window.onerror/unhandledrejection the same way, and ships static fallback content inside the panel so even a script that never runs is not a silent blank page. An unknown screen state now renders the recovery screen instead of an empty string.
  • Loading screens can no longer hang forever when the extension config is missing — LOAD_SPACES/LOAD_APPS/START_DEBUG used to return silently when the saved configuration was absent (e.g. after Reset Configuration while the webview retained old state), stranding the user on a spinner. They now post an explicit error back to the panel.
  • Stopping from VS Code's debug toolbar (red square) now also clears remote breakpoints — Only the panel's Stop button ran the defensive setBreakpoints([]) pass; the toolbar stop skipped it, leaving the remote Node inspector holding breakpoints until cf restart. The clear now also runs on externally-terminated sessions, through the child sessions that briefly outlive the root (best-effort, time-bounded), and removes the now-dead Package-browser breakpoints from VS Code state when no session survives.
  • Breakpoint-clear timeouts sized for slow CF regions — the per-request/total/loadedSources budgets (0.5 s/2 s/1.5 s) could expire on high-latency regions (ap10, jp10), silently resurrecting the "breakpoint survives until cf restart" bug there. Raised to 1.5 s/4 s/3 s; they only bite when the tunnel is half-open.
  • Foreign Debug:-named sessions are left alone — a user-defined launch configuration named Debug: <x> no longer triggers CDS Debug's exited-session cleanup on terminate (notifications, status broadcasts, or the opt-in cf restart of an app the extension does not own).

[0.4.31] — 2026

Fixed

  • Package Browser loads reliably on slow / high-latency CF regions — Clicking Package after starting a debug session could intermittently fail to load any packages (or time out after ~60 s) on slow orgs such as ca10, because the warm-up depended on polling the loadedSources request at exactly the right moment while the child "Remote Process" session appeared. This is now addressed on three fronts:
    • Push-based source collection — CDS Debug now records the DAP loadedSource events that vscode-js-debug emits for every (including child) session, accumulating package sources continuously instead of relying solely on polling. Sources that arrive between polls — or before the browser is opened — are no longer missed.
    • A single slow loadedSources request no longer aborts the whole warm-up — a per-request timeout is treated as "not ready yet" and retried, instead of failing the entire load. One laggy request on a slow inspector tunnel used to kill the attempt outright.
    • Deadline instead of a fixed attempt count — the warm-up now waits up to a total budget (180 s) for the child session to appear, rather than a hard 60-attempt ceiling, and wakes immediately when a new session starts or a source event arrives.
  • More reliable inspector readiness probe — the pre-attach probe now waits for a non-empty /json/list (a real debuggable target) instead of /json/version (inspector metadata only), so vscode-js-debug finds a target immediately and the child session appears dependably.

[0.4.23-pre.1] — 2026

Fixed

  • Package Browser (debug:) breakpoints now turn verified (red) once bound — Breakpoints set in node_modules/package sources opened from the Package Browser as debug: URIs (when the .ts is not on disk) were bound and paused execution, but VS Code's gutter stayed gray because the bind happened via customRequest, which the gutter ignores. The breakpoint mirror now nudges VS Code to re-issue its own setBreakpoints by re-adding the breakpoint once per verifying session (keyed by session + path + line, so no repeated flicker), flipping the dot to red. This complements the file: re-verify fix from 0.4.22.

[0.4.23-pre.0] — 2026

Fixed

  • The Package Browser returns to the launcher when its debug session ends — Stopping the debugger from VS Code (or the remote server detaching/crashing/reconnecting) while the Package Browser was open used to leave an empty Packages screen with no sources. CDS Debug now detects that the browsed app is no longer attached and navigates back to the app-selection (launcher) screen automatically.

[0.4.23] — 2026

Stable release consolidating the 0.4.7-pre.x line (changes since 0.4.4).

Highlights

  • No-install package debugging — the Package Browser opens dependency sources from the running app and no longer writes files into node_modules.
  • Reliable package breakpoints — breakpoints in node_modules/package sources show as verified (red) once their script loads; stopping a session clears remote breakpoints so the app no longer stays paused in the Node inspector (no cf restart).
  • CF instance counts & safe scaling from the panel, and auto-retrying background topology sync after a failed or canceled run.

[0.4.7-pre.14] — 2026

Fixed

  • node_modules breakpoints now show as verified (red) instead of staying gray after the script loads — When a CAP handler in node_modules loads lazily, BreakpointResolver already re-bound the breakpoint via a customRequest (working around vscode-js-debug#1510) so execution paused — but a customRequest does not update VS Code's gutter, so the dot stayed gray. It now also removes and re-adds the matching file: breakpoint once per session (deduped by session + path + line, so no repeated flicker), forcing VS Code to re-issue its own setBreakpoints against the now-loaded script and flip the dot to red. debug: URIs are left to the Package Browser mirror.

[0.4.7-pre.13] — 2026

Fixed

  • Stopping a debug session no longer leaves Package Browser breakpoints stuck in the remote Node inspector — clearBreakpointsBeforeStop now clears file: package breakpoints (opened from the Package Browser) using each session's own sourceReference against the original source path the breakpoint mirror bound, broadcast to every app session, instead of a path-only clear of the local fsPath. The path-only clear silently missed reference-bound copies, leaving the app paused at the breakpoint until a cf restart.

Changed

  • CDS Debug no longer writes package source files into node_modules — The Package Browser previously materialized a .ts served only via sourcesContent to disk. It now opens an already-existing local file read-only when present, otherwise a debug: URI served by the debugger; breakpoints there bind by sourceReference and are cleared on stop. This removes the node_modules pollution and the instability tied to writing files on Windows/WSL.

[0.4.7-pre.9] — 2026

Diagnostics

  • Adds Package Browser breakpoint mirror diagnostics — Logs breakpoint event counts, session/source lookup timings, per-session setBreakpoints verification counts, promotion target selection, same-URI refresh counts, and total mirror duration to make no-src breakpoint flicker and latency diagnosable without changing binding behavior.

[0.4.7-pre.8] — 2026

Reverts

  • Rolls back the unstable 0.4.7-pre.7 Package Browser breakpoint refresh attempt — Restores the 0.4.7-pre.6 code path after real no-src debugging showed the follow-up refresh/cache change did not improve breakpoint behavior.

[0.4.7-pre.6] — 2026

Reverts

  • Reverts the Package Browser breakpoint refresh optimization from 0.4.7-pre.3 — Restores the previous full-file refresh and all-session mirror completion behavior after real no-src package debugging showed the narrower refresh path was not stable enough. The WSL file-URI anchoring fix remains in place.

[0.4.7-pre.5] — 2026

Tests

  • Raises enforced unit coverage above the branch threshold — Adds focused unit coverage for Package Browser source normalization/search/URI tracking, package breakpoint mirroring failure paths, and safe package source materialization. pnpm test:coverage now passes with global branch coverage above 80%.

[0.4.7-pre.4] — 2026

Fixes

  • Cache sync recovers after canceled or failed attempts — Settings still shows the last successful sync plus the latest failed attempt, but retryable failures now schedule an automatic retry outside the normal cache interval. CDS Debug also reconciles stale Settings progress with newer shared cf-sync snapshots so an old canceled attempt no longer appears stuck after another tool has produced a fresh topology.

[0.4.7-pre.3] — 2026

Fixes

  • Reduces Package Browser breakpoint flicker on no-src WSL sessions — Breakpoint mirroring still sends the full source breakpoint set to the debug adapter, but VS Code now refreshes only the breakpoint that was added or edited instead of removing and re-adding every breakpoint in the package file. The UI also refreshes as soon as the first session verifies the breakpoint, without waiting for slower sibling session source lookups.

[0.4.7-pre.2] — 2026

Fixes

  • Keeps no-src Package Browser breakpoints anchored to local file editors on WSL — URI-like debugger paths such as vscode-remote://... are still mirrored to the debug adapter, but verified path-only package breakpoints now refresh the existing file: editor breakpoint instead of migrating it to the remote URI. This preserves VS Code's filesystem-path breakpoint identity so the margin breakpoint stays visible and can bind when the package source executes.

[0.4.7-pre.1] — 2026

Fixes

  • Stabilizes no-src Package Browser breakpoints on WSL-style paths — When a Package Browser file opens through a local file: fallback but the debugger reports the same package source as vscode-remote://..., breakpoint mirroring now promotes the visible breakpoint to that parsed remote URI after the adapter verifies it. This keeps the editor breakpoint identity aligned with the debugger source path without reintroducing the previous double-encoded debug: URI issue.
  • Clears high-severity dev dependency audit findings — Pins transitive fast-uri resolution to the patched 3.1.2 release used under the VSIX packaging toolchain.

[0.4.7-pre.0] — 2026

Reverts

  • Hard-reset code to the v0.4.1-pre.0 baseline — Subsequent fix attempts (9cbe750, f02ba3f, 7907a62, b447ac5) layered on top of the 0.4.1-pre.0 baseline introduced regressions in breakpoint binding for mapped folders. They are preserved on the attempt/materialize-removal branch for future re-investigation, while master rolls back to the last known-good package handling code (commit c535d8c). Only the version is bumped on top of the rolled-back tree to keep the pre-release version monotonically increasing past the previously published 0.4.4.

[0.4.1-pre.0] — 2026

Fixes

  • Stable Package Browser breakpoints for mapped apps — Package Browser now avoids inventing or materializing missing package files under a mapped app folder's node_modules path. Existing local package files still open normally, while missing package sources keep the debugger's source identity so mapped-app package breakpoints behave like the stable no-src flow.
  • No double-encoded verified source URIs — Path-only package sources whose debugger path is already a URI, such as vscode-remote://..., are no longer promoted through asDebugSourceUri(). This prevents broken vscode-remote://.../vscode-remote%3A/... editor focus attempts after breakpoint mirroring verifies the breakpoint.

[0.4.0] — 2026

Highlights

  • Reliable breakpoints — Breakpoints now bind more consistently on first attach across CAP workers, lazily-loaded scripts, package sources, source maps, and Windows path casing edge cases.
  • Faster CF navigation — cf-sync topology now powers more of the org/space/app flow, refreshes orgs during login, keeps the 50-region catalog current, and defers regex remote-folder SSH discovery until Start Debug for selected apps.
  • Shared scope and folder mapping — CDS Debug now syncs the active CF scope through sapCap.currentScope, handles cross-region external scope changes more safely, preserves region mappings, and supports explicit cdsDebug.appFolderMappings.
  • Safer debug lifecycle — Stop/restart now verifies local port cleanup, clears remote breakpoints defensively, detects stale tunnels, probes inspector readiness, and targets the likely main Node process by default.

[0.3.62-pre.34] — 2026

Changes

  • Remote-folder SSH discovery is deferred to "Start Debug Sessions" — Selecting an org/space no longer SSHes into every started app to pre-resolve regex: remoteRoot settings. The probe now runs only for the apps you tick when you click Start Debug, in parallel and cached for the rest of the VS Code session. A lightweight CF session keepalive after org/space selection is preserved so any token expiry is still handled up front. For spaces with dozens of apps the Output channel and CF audit log stay quiet until you actually debug, and each app card briefly shows "Discovering remote folder…" while its cold lookup runs.

[0.3.62-pre.33] — 2026

Changes

  • Adds the eu10-006 Cloud Foundry region — Bumps @saptools/cf-sync to 0.4.10, which adds the eu10-006 (Europe/Frankfurt, AWS) landscape to the synced region catalog. CF topology sync and the region picker now cover all 50 SAP BTP Cloud Foundry regions.

[0.3.62-pre.32] — 2026

Changes

  • Explicit CF app → local folder mappings via cdsDebug.appFolderMappings — A new array setting maps a Cloud Foundry app name to a local source folder name when the two differ too much for the automatic -↔_ normalization to find a match (previously such apps fell back to console-only debugging with no source maps or breakpoints). Each folderName is a folder basename resolved through the existing recursive group-folder scan (depth ≤ 6, must contain a package.json); explicit mappings take the highest matching priority and apply consistently to debug start, target building, and regex remoteRoot warmup. Unset (default []) keeps the previous behavior unchanged. v1 maps by folder basename only; pointing at an explicit path is a possible future addition.

[0.3.62-pre.31] — 2026

Fixes

  • Package Browser breakpoints now bind visibly for path-only file sources — When a package source opens as a file: URI with sourceReference: 0, CDS Debug mirrors the breakpoint to the live debug sessions, reads the adapter's verified=true response, and refreshes the same VS Code breakpoint so the editor UI changes from gray/unbound to red/bound.
  • Package source identity is tracked across file and debug URIs — Package Browser now keeps the originating source path, source reference, and session metadata for opened package files so breakpoint mirroring, tab dedupe, and cleanup all reason about the same logical source.
  • Dependency source maps are included in generated attach configs — Generated outFiles now includes app, workspace, and bounded ancestor node_modules roots, which lets vscode-js-debug verify package breakpoints through its native source-map pipeline.
  • Source-reference package files can be materialized safely — When a package source is only available through DAP source content, CDS Debug can write it to a safe local node_modules path and open it as a normal file: URI instead of forcing a virtual debug-source editor.
  • Auto-attached debug sessions are tracked by session id — Child and worker sessions with repeated display names are retained separately, improving Package Browser source collection and breakpoint propagation.

[0.3.62-pre.19] — 2026

Changes

  • Region login now refreshes orgs through cf-sync — Updated @saptools/cf-sync to 0.4.9 and use its region org-list refresh during Cloud Foundry login, so Step 2 shows the latest orgs without walking spaces or apps.
  • Org-list topology stays a live navigation hint — CDS Debug now treats topology accounts with empty spaces as org-list-only data, preserving live cf spaces fallback until targeted space/app data is synced.

[0.3.62-pre.17] — 2026

Changes

  • Cache sync now delegates topology recovery to cf-sync — Updated @saptools/cf-sync to 0.4.7, moved background CF topology commands back to cf-sync's timeout-backed helpers, and removed CDS Debug's local stale-lock recovery workaround while keeping Change Mapping cancellation responsive.

[0.3.62-pre.16] — 2026

Fixes

  • Cache sync no longer strands Change Mapping — Change Mapping now asks the extension host to stop an in-flight cache sync, background CF sync commands use the extension's timeout-backed CF client, and stale cf-sync locks are recovered before a new manual Sync Now attempt.

[0.3.62-pre.15] — 2026

Changes

  • Topology-first CF navigation — Synced cf-sync topology now carries spaces and apps, letting the launcher skip live cf orgs, cf spaces, and cf apps round-trips on the cached happy path while keeping live fallbacks for misses and space sync errors.
  • Background CF session warmup — Apps loaded from topology render immediately while the extension warms the CF target/session in the background and serializes warmup with Start Debug.
  • First-run cache bootstrap — Saving credentials triggers an immediate background sync, and first login warms the selected cf-sync region when topology is not already available.

[0.3.62-pre.14] — 2026

Fixes

  • External CF scope changes are serialized — Rapid external updates to sapCap.currentScope now queue through one handler, preventing overlapping cross-region auto-logins from leaving the launcher and CF CLI on different targets.
  • CF auth failures return faster — cfLogin now skips retry backoff for clear credential/auth failures while still retrying transient network errors.
  • Remote root warmup is parallelized safely — Started apps now warm regex remote roots in bounded batches of four instead of one at a time.
  • Cache sync skipped attempts are visible — Settings now preserves the last successful sync time and shows the latest skipped/failed attempt reason, such as missing credentials.

[0.3.62-pre.13] — 2026

Fixes

  • Login-shell environment lookup now retries after spawn failures — A failed login-shell environment read no longer caches an empty result for the whole VS Code session, so credentials from shell dotfiles can be found on a later user-triggered retry.
  • Settings preference toggles stay visually in sync — Late preference refresh messages now update the Settings toggle DOM in place, preventing CI-visible races where a saved debug preference could look disabled until reopening Settings.

[0.3.62-pre.12] — 2026

Changes

  • Remote inspector stop reminder is now opt-in — Stopping debug no longer shows the Node inspector restart reminder by default. Teams that still want the reminder can enable cdsDebug.warnRemoteInspectorAfterStop, while automatic app restart remains opt-in via cdsDebug.autoRestartAppAfterStop.

[0.3.62-pre.11] — 2026

Fixes

  • Cross-region shared CF scope errors are now visible and safe — Failed external cross-region auto-login now reports LOGIN_ERROR in the launcher, reuses the credential revocation flow for auth failures, clears stale pending external scopes when a newer credential-backed scope arrives, and redacts cf auth command arguments from CF CLI errors before they reach logs or UI.

[0.3.62-pre.10] — 2026

Fixes

  • External CF scope changes stop active sessions first — CDS Debug now stops active debug sessions, clears breakpoint snapshots, and notifies the user before applying an externally synced org/space change, preventing stale tunnels and cross-region reconnect races.

[0.3.62-pre.9] — 2026

Fixes

  • Shared CF scope folder mapping recovery — External scope sync now opens the 3/3 Select Local Folder step when the target org/space has no saved mapping, and cross-region sync without stored credentials pre-fills the target region for manual login.

[0.3.62-pre.8] — 2026

Fixes

  • Cross-region shared CF scope sync — External updates to sapCap.currentScope from another CF region now trigger a credential-backed auto-login, preserve saved mappings, and reselect the target org/space when available instead of being silently ignored.

[0.3.62-pre.7] — 2026

Changes

  • Remote inspector cleanup hardening — CDS Debug now clears remote breakpoints before stop, warns that the Node inspector may remain open until app restart, offers opt-in auto-restart after stop, detects stale local cf ssh inspector tunnels on activation, warns about local debugger; statements after attach, and uses an app-level keepalive to recover faster from half-open debug tunnels.
  • Safer inspector activation — The default USR1 signal now targets a likely main Node process (server.js, app.js, or index.js) and avoids common sidecars such as cds-mtxs. Set cdsDebug.signalAllNodeProcesses to true to restore the previous all-node behavior.

[0.3.62-pre.6] — 2026

Changes

  • CF region catalog source cleanup — Updated @saptools/cf-sync to 0.4.6, using its catalog for eu10-*, eu20-*, us10-001, and us10-002 region endpoints while keeping CDS Debug's local fallback only for upstream-missing endpoints such as us10-004.

[0.3.62-pre.5] — 2026

Changes

  • Shared CF scope sync — CDS Debug now writes the verified regionCode, org, and space to the VS Code global sapCap.currentScope setting after apps load, and compatible same-region updates from external tools automatically reselect the mapped scope in the launcher.

[0.3.62-pre.4] — 2026

Fixes

  • Org folder mappings now survive CF region switches — Logging into another CF region now preserves all saved local folder mappings instead of deleting mappings for orgs outside the current region. Restore logic now only auto-loads mappings compatible with the active region and prefers the most recently used org/space mapping.

[0.3.62-pre.3] — 2026

Fixes

  • Auto-reconnect can no longer stall on a hung pre-reconnect hook — The beforeReconnect hook that re-runs mergeLaunchJson is now bounded by a 3-second timeout. A locked launch.json, slow disk, or unresponsive cap-debug-config.json read will log a warning and proceed with the existing configuration instead of leaving the session stuck in TUNNELING….
  • Breakpoints in lazily-loaded scripts now bind on Windows when drive-letter casing differs — The DAP loadedSource re-resolve now compares filesystem paths case-insensitively on Windows, where VS Code's Uri.fsPath (C:\…) and the DAP source.path (c:\…) can differ in casing despite referring to the same file.

[0.3.62-pre.2] — 2026

Fixes

  • Breakpoint-bind Sprint 3 advanced cases — Generated launch configurations now set autoAttachChildProcesses: true so SAP CAP MTX sidecar / cluster workers are debugged automatically, ship default sourceMapPathOverrides for the Cloud Foundry runtime layout (/home/vcap/app/*, /home/vcap/deps/0/node_modules/*, plus the existing webpack defaults), and a new debug-adapter tracker re-issues setBreakpoints after loadedSource events so breakpoints land in lazily-required scripts that were eagerly loaded before attach completed (workaround for microsoft/vscode-js-debug#1510).
  • Breakpoint snapshot handling default is now fail-safe — When the preferences store is unavailable, snapshot handling reports as disabled instead of accidentally enabling the auto-continue UX, and the first auto-continue per session surfaces an informational notification with shortcuts to the relevant settings.

[0.3.62-pre.1] — 2026

Fixes

  • Breakpoint-bind Sprint 2 cleanup — Generated launch configurations no longer set restart: true so vscode-js-debug stops racing the extension's own auto-reconnect, the regex remoteRoot warning surfaces in a one-shot VS Code notification with actions to open the offending cap-debug-config.json or the CDS Debug output channel instead of failing silently, and auto-reconnect re-runs mergeLaunchJson before the next attach so edits to cap-debug-config.json made mid-session are picked up.

Changes

  • cap-debug-config.json and cdsDebug.sharedCapDebugConfig schema extended — Added outFiles, outFilesExtra, resolveSourceMapLocations, and sourceMapPathOverrides fields with strict type guards so users can replace, append to, or refine the source-map handling produced by the extension without hand-editing launch.json.

[0.3.62-pre.0] — 2026

Fixes

  • Breakpoints bind on the first attach (Sprint 1 of breakpoint-bind hardening) — Generated launch configurations now expand outFiles to cover srv, gen/srv, app, lib, dist, and build (excluding node_modules), set resolveSourceMapLocations: null so source maps with embedded remote paths are no longer silently dropped, resolve localRoot through fs.realpath to handle macOS /private/var/... symlink workspaces, and fall back to localRoot when a regex remoteRoot is configured but has not yet resolved — eliminating the "Stop and Start again to bind" workaround for several common configurations.

[0.3.61-pre.1] — 2026

Fixes

  • Verified SSH tunnel cleanup — Stop and debug-session termination now await local debug port cleanup and verify the port is free before fast restarts, preventing confusing address already in use failures when restarting the same CF app quickly.

[0.3.61-pre.0] — 2026

Security

  • Branch preparation RCE hardening — Replaced shell-based git and pnpm execution with execFile argument arrays, added strict branch-name validation for cap-debug-config.json and cdsDebug.sharedCapDebugConfig, and surface unsafe branch config warnings without logging payloads.

[0.3.61] — 2026

Fixes

  • Custom endpoint flow — Moved custom CF API endpoint entry out of the scrollable region list into a dedicated Region tab panel action, keeping the 1/3 CF Region / Org header, selector tabs, and Login to Cloud Foundry footer position stable.

[0.3.60] — 2026

Changes

  • CF region catalog — Completed the 1/3 CF Region / Org picker supplemental endpoints from SAP's Cloud Foundry region table, adding eu10-002, eu10-003, eu10-005, eu20-001, eu20-002, us10-001, and us10-002 while keeping the product-supported us10-004 endpoint.

[0.3.58] — 2026

Changes

  • CF region catalog — Added the eu10-004 Cloud Foundry region to the 1/3 CF Region / Org picker with endpoint https://api.cf.eu10-004.hana.ondemand.com.

[0.3.57] — 2026

Fixes

  • Change Mapping navigation — The launcher now returns to 1/3 CF Region / Org when changing mappings, so users can choose a different CF region or org from the start of the mapping flow.

[0.3.54] — 2026

Changes

  • Wider VS Code compatibility — Lowered the minimum required VS Code engine from 1.118 to 1.112, so users on VS Code versions from 1.112 onwards can install and use CDS Debug without needing to be on the very latest editor release.

[0.3.53] — 2026

New Highlights

  • Dynamic remote roots — Regex-based remoteRoot settings resolve per CF app before debug attach, covering services deployed under different remote folders such as /usr/sample-service-a.
  • Compatibility refresh — VS Code 1.118 engine support and refreshed CF sync, ESLint, TypeScript ESLint, and VS Code API dependencies.

[0.3.10] — 2026

New Features

  • Package Browser — Browse every npm package loaded in an active debug session as a collapsible tree. Jump to any source file inside a package without navigating node_modules manually.
  • Package Regex Filter — Filter the package list by name using a regex. Pre-configure a default via cdsDebug.packageRegexFilter in workspace or user settings; edits in the UI sync back automatically.
  • Auto-reconnect — SSH tunnel reconnects automatically (up to 3 attempts) when a CF timeout or network blip drops it mid-session.
  • Breakpoint Snapshots — Capture variable context at any breakpoint without pausing execution. Snapshots accumulate in the sidebar. Enable in Settings → Breakpoint Snapshot Handling.
  • Branch Preparation — Stash local changes, check out the target git branch, and run pnpm install && pnpm build before attaching the debugger so local sources always match the remote service.
  • Shared CAP Debug Config — Set cdsDebug.sharedCapDebugConfig once in VS Code user settings to share remoteRoot and orgBranchMap across all workspaces.
  • What's New panel — Displays automatically after a version upgrade so you always know what changed.

Bug Fixes

  • Suppress VS Code's save-before-start behaviour for extension-managed debug sessions, preventing spurious permission-denied errors when an unrelated editor is open at a root path.
  • Package entries reload correctly when a debug session is restarted.
  • Source maps for generated CAP server files resolve from the correct output path.

[0.3.0]

  • Breakpoint snapshot handling foundation (capture + display).
  • Auto-continue after snapshot capture (configurable via cdsDebug.pauseOnBreakpoint).
  • Performance improvements for snapshot capture latency.

[0.2.41]

  • Shared cdsDebug.sharedCapDebugConfig VS Code setting as a workspace-level fallback.
  • Region picker — 14 built-in CF regions plus custom endpoint support.

[0.1.0]

  • Renamed "Auto-open app in browser" to "Open browser on debugger attach" with live state badge.
  • Multi-select debug — tick any running apps and launch all sessions at once.
  • Background app cache with configurable sync interval.

[0.0.25]

  • Region-switch fix: stale CF session cleared before switching regions.

[0.0.21]

  • Select-all, Stop-all, Refresh, port display, theme badges.

[0.0.19]

  • Various UI bug fixes and webview polish.
Assets 2
Loading