Module not found error when k6 fails to resolve a local import
When running a k6 test that imports a local JavaScript module, the tool aborts with a “module not found” error before any virtual users start. The goal is to understand exactly how k6’s ES‑module resolver determines the file location for relative imports, especially when the test is launched from a directory different from the test file or when symlinks are
k6