Dependency RadarWebStorm plugin
Know what your npm package can affect before you publish it
Find affected projects, reveal the dependency path, and act before publishing—right inside WebStorm.
Free early access · no card required
The real demo
See Radar at work
Nine real screens, from consumer discovery to the action journal.
Version, relationship kind, active Git branch, and dirty status sit beside every discovered project.
The selected storefront expands into a transitive chain through ui-kit to the current design-tokens package, with versions at each step.
Select multiple consumers in the table, then run one configured action for the whole group.
Successful and failed commands remain inside the plugin with full output and the originating project.
Search, branch selection, and service filters narrow the list without losing the surrounding context.
The built-in version update can be extended with custom commands for single or bulk execution.
An in-product legend explains direct, linked, transitive, lockfile-only, and fallback results.
When the current project cannot be scanned, Radar explains why instead of showing an empty or misleading result.
The essential data remains usable in a narrow side panel while the editor keeps most of the workspace.
01 / Scenario: analysis
From one package to every consumer
Follow design-tokens into apps across neighboring repositories. No monorepo migration required.
- 01
Open the package
Open design-tokens in WebStorm. Radar identifies its name, version, and package manager.
- 02
Choose project roots
Point Radar to your apps and libraries. It connects manifests, lockfiles, and local links.
- 03
Trace the impact
Expand storefront → ui-kit → design-tokens. Compare versions and choose the projects to update.
02 / Scenario: Pipelines
One Pipeline from package build to every consumer
Pipelines connect the build, npm publication, new version, consumer updates, and dependency installation in a repeatable flow.
Make it fit your workflow
- Create a Git branch with the same name across multiple repositories
- Publish several packages in parallel
- Add your own commands and choose their order
design-tokens- 01Build
- 02Publish to npm
- 03New version
storefrontadmin-appdocs- 01Shared Git branch
- 02Update version
- 03Install dependencies
One Pipeline for the whole release
03 / More capabilities
Everything needed for the decision, in one window
Complete graph
Direct, transitive, and lockfile-only paths with versions.
Local relationships
Workspaces, Yarn PnP, links, symlinks, and worktrees.
Git context
Branch, dirty status, and worktrees beside every project.
Actions and Journal
Single and bulk commands with retained output.
Who the first release is for
For multi-repo teams and shared-package authors
- Design systems, SDKs, and shared UI
- Multiple repositories, branches, or worktrees
- npm, Yarn, and pnpm with local links
Product model
The impact map will stay free
Advanced automation will be part of a paid edition.
For regular impact checks
- Every consumer type
- Paths, versions, and Git context
- Essential actions
For automation and complex graphs
- Bulk actions
- Advanced Git and worktree workflows
- Tools for large graphs
Final boundaries and pricing will be announced before launch.
Technical detail
Discovery model and boundaries
Implementation detail when you need it.
Open technical details+
How discovery works
Dependency Radar starts with the package opened in WebStorm and scans the configured local project roots. It combines several kinds of evidence instead of treating a text match as the complete answer:
package.jsonmanifests reveal direct and transitive relationships between local packages.yarn.lock,package-lock.json, andpnpm-lock.yamlreconstruct installed paths that may not be visible in manifests alone.- Yarn Classic and modern PnP, workspaces, npm/pnpm links, symlinks or junctions, and
file:,link:, orportal:references reveal projects that resolve to the currently open package. - Git metadata adds the active branch, dirty status, and related worktrees to each result.
Every match is classified by its source. When a path is inferred or ambiguous, the UI says so rather than presenting it as certain. Ordinary pnpm virtual-store symlinks are filtered so they do not look like intentional local links.
From evidence to action
Open a dependency path to see package versions and dependency kinds at every step. Search and filter the result set, compare the consumer’s requested version with the current package, then open the project, switch to a branch or worktree, set the target version, or run a configured action. Single and bulk operations are recorded in the Journal.
Dependency Radar also shows the detected package manager and version, the package’s publishing intent, and whether the current version is already present in the configured npm registry.
Current beta boundaries
- The beta supports WebStorm 2026.1 and 2026.2.
- Dependency analysis currently focuses on npm packages and npm, Yarn, and pnpm project structures.
- Graph depth, path count, and project discovery limits are configurable to keep large roots responsive.
- Compound semver ranges and some non-registry references can be marked as inferred instead of being treated as exact graph edges.
- Beta access and installation are handled manually while the feedback and update process is being refined.
The beta is intended for use on real projects, but it is pre-release software. Keep your repositories under version control and review file-changing or publishing actions before confirming them.
Release history
- Added direct, transitive, and lockfile-only dependency discovery for npm, Yarn, and pnpm projects.
- Added dependency paths with versions, dependency types, inferred-path warnings, and cycle detection.
- Added project search, branch and service filters, Git dirty status, branches, and worktree actions.
- Added single and bulk dependency actions, including setting the target package version.
- Added publishing intent and registry status, configurable graph limits, and the action journal.
- Added support for WebStorm 2026.1–2026.2.
Short answers
Before you apply
Do I need a monorepo?
No. Radar is designed for multiple local repositories.
Are yarn link, PnP, and symlinks detected?
Yes: Yarn Classic/PnP, workspaces, local protocols, and real symlinks or junctions.
Does project data leave my machine?
The graph is built locally. Network access is only used for explicit registry operations.
What does early access cost?
Early access is free. The core map will stay free; advanced features will be paid.
Early access
Try Radar on a real project
The beta build is available by request in exchange for brief feedback.
What you get
- The build and instructions
- Help with the first scan
- A say in product priorities
What helps
- WebStorm 2026.1 or 2026.2
- A real multi-repo project
- Brief feedback
- 1Send a short application
- 2Receive the build and install steps
- 3Run Radar against your repositories
This opens a short pre-filled email about your environment.
Know the right team?