Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not locate bindings file

See original GitHub issue

I’ve just upgraded to 2.18.0 and faced with this issue

    Could not locate the bindings file. Tried:
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/build/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/build/Debug/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/build/Release/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/out/Debug/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/Debug/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/out/Release/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/Release/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/build/default/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/compiled/10.16.0/darwin/x64/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/addon-build/release/install-root/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/addon-build/debug/install-root/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/addon-build/default/install-root/deasync.node
     → /Users/stanleynguyen/Documents/Projects/template-node/{{cookiecutter.service_name}}/node_modules/deasync/lib/binding/node-v64-darwin-x64/deasync.node

      at bindings (node_modules/bindings/bindings.js:126:9)
      at Object.<anonymous> (node_modules/deasync/index.js:30:31)
      at Object.<anonymous> (node_modules/express-openapi-validator/dist/framework/json.ref.schema.js:4:19)

Does anyone know what might be the potential cause?

Issue Analytics

State:
Created 4 years ago
Comments:12 (8 by maintainers)

Top GitHub Comments

1reaction

cdimasciocommented, Dec 1, 2019

Yes. the blocking parse certainly makes usage more straightforward. unfortunately to parse json ref’s, asynchronicity is necessary. the synchronous install is still part of v3 and can be used with installSync. that being said, installSync requires deasync and as we’ve seen, deasync has been at the root of many recent issues.

0reactions

cdimasciocommented, Dec 3, 2019

fixed in v3.0.0

default behavior is async. users can still use the legacy synchronous mode with deasync by using the installSync(...) method. In the sync case, users may encounter incompatibilities with deasync and node