node-gyp: gyp: binding.gyp not found (cwd: C:\Users\xxxx) while trying to load binding.gyp

Hi,

I have followed the below steps to install PWA.

https://magento-research.github.io/pwa-studio/venia-pwa-concept/setup/

But when trying to install build tools and configure the python dependency, we are facing this issue in windows 10. gyp: binding.gyp not found (cwd: C:\Users\xxxx) while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1

And also we have tried the same steps in ubuntu system and it results the following error.

make: *** No targets specified and no makefile found. Stop.

So, kindly let us know how to fix this.

Thanks,

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

  • Try to resolve the missing file issue first:
  • gyp: binding.gyp not found (cwd: D:\PWA) while trying to load binding.gyp
  • Create the file manually ‘binding.gyp’ and add this content to it:
  • Change the path for the source Mac OS’s normally goes in ( /usr/local/bin/node )
{
    "targets": [{
        "target_name": "binding",
        "sources": [ "<PATH TO NODE>" ]
    }]
}

If the file is not there, then this is not an issue with node-gyp, but with the whatever project you are trying to build. You should report it to the package authors.

same issue! Any suggestion? gyp: binding.gyp not found (cwd: C:\node_modules) while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1

I’m going to close this due to staleness but as the above comment says, the node-gyp rebuild --verbose output should be generated within the directory of the addon that’s failing. The above output has gyp: binding.gyp not found (cwd: D:\PWA) while trying to load binding.gyp – if you are creating an addon inside D:\PWA then this simply means you need to create an appropriate binding.gyp in there. IF you are having trouble building a dependency addon, cd into node_modules\whateveraddon and do the node-gyp rebuild in there. There should be a binding.gyp in that directory, or it’s not a proper addon and maybe this isn’t node-gyp’s problem.

for example,cd node_modules/ffi,then node-gyp rebuild