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
The only issue that might arise is that node-gyp is a dep of npm and if it fails, AFAIR it will propagate to fail npm. For most users that's an unneeded fails.
@refack I admit this is not specifically a node-gyp concern. I guess the question is how are we intended to communicate these kinds of requirements?
For example, if you don't know that python is required when you install node-gyp - you only learn so when trying (and failing) to actually use node-gyp. Which, I think it might be better to at least emit a warning on the install phase.
This is especially easy to run into if for example you are constructing a custom node image.
This would be helpful to know during the install phase of node-gyp. Is there any reason not to fo this?
The text was updated successfully, but these errors were encountered: