fix vsce ivocation in cron

[garyverhaegen-da]

It looks like without this change, bazel run @daml_extension_deps//vsce/bin:vsce runs with $PWD set to the folder where the vsce executable is. At least on my machine. This seems really weird.

[cocreature]

Good catch! I actually wonder if we don’t need to do the same for yarn. Afaik, bazel run will always run in some weird working directory.

[garyverhaegen-da]

Trying it locally, it does not look like we need it for yarn. I have no idea why. The internet seems to say the original behaviour was to run in a random directory, but that supposedly has been changed to run under the current directory (where bazel run was invoked) about 6 months ago.

[cocreature]

Hm, maybe it is something about the nodejs_binary thing that messes up the working directory? If it works I’m happy 🙂