needs go.work if using mono repos

[gedw99]

These examples fail if your inside a repo and works if your outside one.

inside a repo meaning where your have a go.mod above you in the file hierarchy.

xk6 build --output xk6-browser --with github.com/grafana/xk6-browser=.

xk6 build --with github.com/grafana/xk6-output-template

The way around this is to generate a touch go.work and then go work use ./xxx to point to where the golang that xk6 is pulling lives on disk, using a simple relative pathing.

I guess xk6 uses home tmp though ?

SO I could not figure out what this needs to be for me...

go work use ./xxx 

Anyone got some ideas :) ?

[szkiba]

Thank you for reporting this.

This is a known bug and we are planning to fix it. Currently, disabling go work is the recommended workaround.

This can be done by setting the GOWORK environment variable to off. This (for linux & osx) can also be done at the beginning of the xk6 command line:

GOWORK=off xk6 build --output xk6-browser --with github.com/grafana/xk6-browser=.

[gedw99]

thanks @szkiba for acknowledging the bug.

I still have to use go work, because of how my users use the system.

I guess I will just have to wait this out until you fix it.

I am pretty sure its just a matter of telling the system where the golang code will be checked out too, and then telling go work with go work use .....