Hello how can I solve getting bindings files error

MeliL · December 4, 2018, 9:12am

hello how can I solve getting bindings files error

/rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/bindings/1.3.1/node_modules/bindings/bindings.js:99

throw err

^

Error: Could not locate the bindings file. Tried:

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/build/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/build/Debug/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/build/Release/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/out/Debug/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/Debug/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/out/Release/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/Release/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/build/default/better_sqlite3.node

→ /rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/compiled/8.14.0/linux/x64/better_sqlite3.node

at bindings (/rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/bindings/1.3.1/node_modules/bindings/bindings.js:96:9)

at Object.<anonymous> (/rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/lib/database.js:4:40)

at Module._compile (module.js:653:30)

at Object.Module._extensions..js (module.js:664:10)

at Module.load (module.js:566:32)

at tryModuleLoad (module.js:506:12)

at Function.Module._load (module.js:498:3)

at Module.require (module.js:597:17)

at require (internal/module.js:11:18)

at Object.<anonymous> (/rbd/pnpm-volume/aaec3d2d-aebb-4535-97bc-3451acb56ac6/node_modules/.registry.npmjs.org/better-sqlite3/4.2.0/node_modules/better-sqlite3/index.js:2:18)

cori · December 4, 2018, 12:46pm

Hi @MeliL, welcome to the Glitch Forums!

This error can be caused by faulty caching on reinstall, and can often be resolved by using the enable-pnpm command in your project’s console:

Hope this helps, and happy Glitching!

MeliL · December 4, 2018, 6:36pm

Thanks
It was dissolved

MeliL · January 24, 2019, 9:21pm

Please don’t help when you write-pnpm, please help!

cori · January 24, 2019, 10:56pm

Hey @MeliL do you mean that you’re getting the error again and enable-pnpm isn’t resolving it? Can you provide your project name?

MeliL · January 25, 2019, 12:01am

first the error was corrected when enable-pnpm, but then it started to exit again and now it doesn’t get improved when it comes to write-pnpm

project name:
salty-airport

cori · January 25, 2019, 4:59am

Hey @MeliL it looks like this issue might be resolved in the most recent version of better-sqlite3, but it looks like you already tried that. You do have quite a few out-of-date packages and you could try updating them if for no other reason than to rule them out as contributing causes.

Another option is to change to a different sqlite library than better-sqlite3 - almost all of the bindings errors like this that we’ve seen are with that specific package, so a different sqlite package might help solve your problem.

cori · January 25, 2019, 2:34pm

Hey @MeliL I have one more thing for you to try. In your projects console can you run rm shrinkwrap.yaml and then run enable-pnpm? I suspect that there’s a broken dependency tree cached in your shrinkwrap file, and removing it and running a fresh install might get you up and running again.

MeliL · January 25, 2019, 4:43pm

thanks improved

Thank you again for your help and for your support

cori · March 28, 2019, 2:54pm

10 posts were split to a new topic: Memwatch-next causing bindings errors