Closed IamKoN closed 6 months ago
Try
./k6 run vendor.js
If you run ./k6 version What do you get?
Try
./k6 run vendor.js
If you run ./k6 version What do you get?
k6.exe v0.50.0 (go1.22.2, windows/amd64) Extensions: github.com/grafana/xk6-sql v0.4.0, k6/x/sql [js]
./k6 run vendor.js
worked, thank you! Not sure why that made the difference, but much appreciated.
Try ./k6 run vendor.js If you run ./k6 version What do you get?
k6.exe v0.50.0 (go1.22.2, windows/amd64) Extensions: github.com/grafana/xk6-sql v0.4.0, k6/x/sql [js]
./k6 run vendor.js
worked, thank you! Not sure why that made the difference, but much appreciated.
When you build k6 with extensions, it creates a new binary. So you'd execute it that why. If you check the log out put of when it was created, there is a message there explaining :)
k6 script, vendor.js:
project directory:
cmds used to build xk6-sql binary:
both work to create the binary in the working dir, but when running
k6 run vendor.js
I get the same error each time: