Cannot update to rules_go to 0.18.7 or later

[alexeagle]

Looks like a change in rules_go
bazel-contrib/rules_go@4442d82
made Runfiles resolution no longer work the way we rely on in ts_devserver.

error looks like https://circleci.com/gh/bazelbuild/rules_nodejs/27670

Could not find runfile build_bazel_rules_nodejs/packages/protractor/test/protractor-2/_devserver_launcher.amd_names_shim.js, got error Runfile build_bazel_rules_nodejs/packages/protractor/test/protractor-2/_devserver_launcher.amd_names_shim.js: could not locate fileFailed to read script build_bazel_rules_nodejs/packages/protractor/test/protractor-2/_devserver_launcher.amd_names_shim.js: open : no such file or directory

However if I throw this code in there

other, _ := bazel.Runfile("packages/protractor/test/protractor-2/_devserver_launcher.amd_names_shim.js")
	fmt.Printf("other runfile %v\n", other)

it prints

other runfile /usr/local/google/home/alexeagle/.cache/bazel/_bazel_alexeagle/c410d6070ef2d359d26ac4aeb886e1ea/sandbox/linux-sandbox/757/execroot/build_bazel_rules_nodejs/bazel-out/k8-fastbuild/bin/packages/protractor/test/protractor-2/devserver_test_chromium-local.runfiles/build_bazel_rules_nodejs/packages/protractor/test/protractor-2/_devserver_launcher.amd_names_shim.js

which makes me think that the runfile now has to be workspace-relative instead of workspace-absolute?

[alexeagle]

I commented on the PR that introduced the change: bazel-contrib/rules_go#2076

[alexeagle]

For now I worked around this issue by patching out the breaking commit:
bazelbuild/rules_typescript@73ba776

keeping this open since we will eventually get a merge conflict with that patch in a future rules_go release.

[alexeagle]

resolved in 148c85b#diff-17471a9d90f9bf767b65c15cd2d3a418c75368934b62acc8490949e9b990f37a