You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is very weird as it only happens if node_or_tools is part of a package.json with other packages, but it doesn't happen if node_or_tools is the only package in the package.json file.
Node version is v10.11.0
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/node_or_tools/v1.0.6/Release/node-v64-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error Connection closed while downloading tarball file
ACTION binding_gyp_action_before_build_target_install_deps mason_packages
ACTION binding_gyp_action_before_build_target_install_deps mason_packages
Downloading Mason @ca9b4cb
Downloading Mason @ca9b4cb
* Downloading binary package osx-x86_64/protobuf/3.0.0.tar.gz...
* Downloading binary package osx-x86_64/protobuf/3.0.0.tar.gz...
* Installed binary package at /xxx/node_modules/node_or_tools/mason_packages/osx-x86_64/protobuf/3.0.0
* Linking /xxx/node_modules/node_or_tools/mason_packages/osx-x86_64/protobuf/3.0.0
* Links will be inside /xxx/node_modules/node_or_tools/mason_packages/.link/
* Using bash fallback for symlinking (install lndir for faster symlinking)
mv: cannot stat '/xxx/node_modules/node_or_tools/mason_packages/.binaries/osx-x86_64/protobuf/3.0.0.tar.gz.tmp': No such file or directory
The text was updated successfully, but these errors were encountered:
It seems that for some reason ACTION binding_gyp_action_before_build_target_install_deps mason_packages is called twice, which causes the issue? Any ideas why that might happen?
This is very weird as it only happens if
node_or_tools
is part of apackage.json
with other packages, but it doesn't happen ifnode_or_tools
is the only package in thepackage.json
file.Node version is v10.11.0
The text was updated successfully, but these errors were encountered: