Vasilios Pantazopoulos
Vasilios Pantazopoulos
I dunno if it is a good enough fix, but looking at that prospective PR it seems pretty simple. Any chance it can get escalated?
Just to give some public feedback: I'd love to see this get updated as well! #subscribe
Is there any planned next-steps on this? Or is it just a big question-mark still? We have similar issues where we can't use `npm_install` due to failures with modules installing...
*clarification, our issue with node modules and `node-gyp` is explicitly when executing in our Linux docker container on CI, however it works fine on our local MacOS machines.
@xvzf No, although we're diving back into looking more at it now.
for now, I think we've found a workaround with using `npm_command = "install"`, as it's only when `bazel` runs `npm ci` in these environments that it seems to fail to...
Ok, so our issue isn't purely with `node-gyp-build` but rather that, when it executes, it can't find `node-gyp`. Which shouldn't be a thing seeing that `node-gyp` is a pack-in with...
I was hoping this was maybe due to something with symlinked paths, assuming it was executing the `node-gyp` from within `utf-8-validate`'s build (that's who's using `node-gyp-build`), and during that install...
Ok, one last update: this isn't Linux specific. We're seeing the same issue on our MacOS containers as well.
phooey, the "globally install" trick isn't working on our MacOS containers :/