Skip to content

Veyra Blast Radius 1.0.0: know what your change can break before you commit - #37

Merged
fcopensource merged 1 commit into
mainfrom
blast-radius-extension
Nov 17, 2026
Merged

fcopensource merged 1 commit into
mainfrom
blast-radius-extension

Conversation

@fcopensource

Copy link
Copy Markdown
Owner

A new, original VS Code extension (not a copy of an existing one): Veyra Blast Radius.

What it does

It reads every import in the project and walks them backwards from your uncommitted changes, so you see everything your change can break before you commit.

  • Blast Radius view in Source Control, grouped into Tests to run, Routes/pages/APIs, Components, Config & middleware and Other code, with a count badge and a status bar item
  • Interactive graph: changed files in the middle, one ring per import hop; hover traces the path, click opens the file
  • Run Affected Tests in one click: Vitest, Jest, Mocha, Playwright, node --test, pytest, or a custom command
  • "Used by N files · blast radius M" CodeLens on every source file
  • Why Is This Affected? shows the import chain; Show Blast Radius of This File from the Explorer or an editor tab
  • Deleted files still show everything that imported them
  • Copy Impact Report (Markdown) for pull requests
  • JavaScript, TypeScript, Vue, Svelte, Astro and Python; tsconfig/jsconfig path aliases and baseUrl (monorepos too), ESM .js → .ts
  • 100% local: reads files and runs git status, nothing sent anywhere. Restricted Mode supported (no git or tests).

Also in this PR

  • blast-radius added to the Publish VS Code extension workflow
  • A row in the repo README's extension table
  • The tested .vsix in extensions/blast-radius/release/

Tested

  • 18 unit tests for the engine (imports, aliases, Python, cycles, depth limit, classification, runner detection, git status parsing)
  • 8-step integration test inside real VS Code on a sample git project: uncommitted change → importers through the @/ alias, tree groups and badge, CodeLens counts, live updates on save, Python, deleted file, report, graph. It caught a Windows drive-letter path bug, now fixed.
  • Packaged .vsix: 76 KB, 9 files

After merging

Publish it from Actions → Publish VS Code extension → blast-radius.

🤖 Generated with Claude Code

…commit

A new, original VS Code extension. It reads the imports of a JS/TS/Vue/
Svelte/Astro/Python project (tsconfig path aliases, baseUrl, ESM .js->.ts,
Python packages and relative imports) and walks them backwards from your
uncommitted changes:

- a Blast Radius view in Source Control, grouped into tests, routes/pages/
  APIs, components, config and other code, with a badge and status bar count
- an interactive graph (changed files in the middle, one ring per hop,
  hover to trace the import path, click to open)
- Run Affected Tests (Vitest, Jest, Mocha, Playwright, node --test, pytest
  or a custom command), "Used by N files" CodeLens, Why Is This Affected?,
  blast radius of any file, deleted-file importers, Markdown impact report

18 unit tests and an 8-step integration test in VS Code (which caught a
Windows drive-letter path bug, fixed). Added to the publish workflow and the
repo README; the tested .vsix is in release/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fcopensource
fcopensource merged commit b7dbaf8 into main Nov 17, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants