Vexal Releases

Features Released in v1.5.0

vx overview gives you repo structure at a glance — total file count, edge count, and the top 10 most-depended-on files ranked by how many files depend on them. One command to orient yourself or your AI agent to an unfamiliar codebase before making changes.
vx init now injects @.vexal/CLAUDE.md into your root CLAUDE.md automatically so Claude Code loads vexal context in every session without any manual setup. The generated file now includes your repo's live edge count so Claude calibrates how aggressively to use vexal based on actual codebase scale.
vx deps and vx impact now accept file paths without extensions — vx deps src/components/App resolves the same as vx deps src/components/App.tsx.
Duplicate import paths no longer appear in vx deps output.

vx impact and vx deps now correctly track multi-line TypeScript imports. Previously, imports where the named bindings spanned multiple lines — import {\n foo,\n bar,\n} from './module' — were silently skipped, causing callers to be missing from impact results. On Excalidraw, this fix surfaces 626 additional edges (3,541 → 4,167). Upgrade recommended — run vx init after upgrading to rebuild your snapshot with the corrected edge data.

vexal now tracks which commands get run. No personal information is collected — what gets tracked is command name, OS, vexal version, and whether it came from an interactive session or CI. This helps me understand what's working and where to focus next.

vexal is now available on Linux. Install via Homebrew (brew install pinedavictor/vx/vexal) — the same tap that serves macOS now serves Linux x64 as well.

vexal is now available on Windows. Install via Scoop: scoop bucket add vexal https://github.com/PinedaVictor/scoop-vexal then scoop install vexal.

vexal is now available on npm. Install globally with npm install -g vexal. The package uses optional platform-specific binaries — npm selects the right one for your OS and architecture automatically.