optionsvalid.d.ts changes across machines

[aptenodytes-forsteri]

Here, ts_project_options_validator.js writes process.argv[1] to the file:

https://github.com/bazelbuild/rules_nodejs/blob/43e478dd48cea53dbcc580da92ccb517534b832d/nodejs/private/ts_project_options_validator.js#L130

For us, this resolves to something like:

/home/jenkins_user/local-bazel-output-base/sandbox/linux-sandbox/9011/execroot/<workspace>/bazel-out/host/bin/external/path/to/ts_project_options_validator.js

So different build machines might populate the remote cache with different values, or local builds might unnecessarily differ from the remote cache. Does it make sense to remove this absolute path from the optionsvalid.d.ts file?

[fparga]

Duplicate of https://github.com/bazelbuild/rules_nodejs/issues/3461

[fparga]

Fixed by https://github.com/bazelbuild/rules_nodejs/pull/3462

Available in release 5.5.1

[aptenodytes-forsteri]

Glad it's fixed!