Dep Beacon

Follow the signal

06 / Your workflow

Make it yours.

The defaults get you started. Adjust your registry, security queries, and editor signals when your workspace needs something different.

Start with your editor

In VS Code, use Settings or .vscode/settings.json. In Zed, place language-server settings underlsp.dep-beacon.settings. These examples show the defaults; add only the overrides you need.

json
{
  "depBeacon.enable": true,
  "depBeacon.includePrerelease": false,
  "depBeacon.checkVulnerabilities": true,
  "depBeacon.registryUrl": "https://registry.npmjs.org",
  "depBeacon.cacheTtlMinutes": 15,
  "depBeacon.showInlineStatus": true,
  "depBeacon.runInstallOnSave": false,
  "depBeacon.packageManager": "auto"
}

VS Code settings at a glance

Each setting below uses the depBeacon. prefix.

VS Code settings and their default values
SettingDefaultWhat it controls
enabletrueEnable CodeLens, diagnostics, and inline dependency status.
includePrereleasefalseInclude prerelease versions when calculating update targets.
checkVulnerabilitiestrueQuery OSV.dev for vulnerability summaries.
showInlineStatustrueDisplay colored labels beside version ranges.
cacheTtlMinutes15Reuse document analysis for 1–1440 minutes.
runInstallOnSavefalseRun a package install after saving a supported manifest.
packageManagerautoDetect the manager automatically, or select npm, pnpm, or yarn.

Registry and cache

registryUrl
Defaults to https://registry.npmjs.org. It can point to another npm-compatible registry. Package links still open npmjs.com.
Fresh metadata
In VS Code, run Dep Beacon: Clear Registry Cache when you publish a package and want to refresh cached results immediately.
Zed diagnostics
Set showUpdateDiagnostics to false to hide update warnings. Security findings, manifest errors, hovers, and update actions remain available.