Therefore, in some cases, it's more reliable to run ginkgo via go modules: go run github.com/onsi/ginkgo/v2/ginkgo (relevant change in a codebase I maintain: https://github.com/alphagov/paas-cf/pull/2998).
It would be great if it were possible for ginkgoTestExplorer to 'fail-over' to using the go run syntax when the executable is unavailable, to avoid these possible mismatches.
I've attempted to do this myself, but my TypeScript / nodejs is just not up to it.
Recent changes to ginkgo have essentially decoupled the CLI tool and library versions: https://github.com/onsi/ginkgo/releases/tag/v2.3.1
Therefore, in some cases, it's more reliable to run ginkgo via go modules:
go run github.com/onsi/ginkgo/v2/ginkgo
(relevant change in a codebase I maintain: https://github.com/alphagov/paas-cf/pull/2998).It would be great if it were possible for ginkgoTestExplorer to 'fail-over' to using the
go run
syntax when the executable is unavailable, to avoid these possible mismatches.I've attempted to do this myself, but my TypeScript / nodejs is just not up to it.