k6 deps analyzes script and archive dependencies
Introduced 2026-02-10 · score 0.97
HOW TO USE IT
When you need to identify script or archive dependencies for an auto-resolved build, run `k6 deps <script-or-archive>`; add `--json` for programmatic output. The command reports dependencies found through imports and “use” directives, but does not follow dynamic `require()` calls.
k6 deps <script.js>k6 deps --json <script.js>k6 deps <archive.tar>WHY THIS HELPS
Inspect a script or archive to identify extension dependencies needed to build a binary with auto extension resolution.
REQUIREMENTS AND LIMITATIONS
- Version: v1.6.0
- <script> (required): Script or archive to analyze.
- --json: Output dependency information in JSON; default output is human-readable.
- Dependency analysis accounts for imports, not dynamic `require()` calls.
FIRST-PARTY EVIDENCE
- https://github.com/grafana/k6/releases/tag/v1.6.0
- https://grafana.com/docs/k6/latest/release-notes/v1.6.0/
- https://grafana.com/docs/k6/latest/using-k6/k6-deps-command/
Check the installed version and the source before using it. Entry JSON