node searching in 'node-v11-darwin-x64', fails to find 'node_sqlite3.node' #228
|
For now you need to do |
|
Okay, I'll follow it in that issue. Thanks. Should I close this issue, then? |
|
I am trying to use this module in a |
|
@mtrpcic the current workaround is to manually copy the binary into the right place. |
|
I'm having the same issues.. can you explain "manual copy the binary into the right place" a little more? |
|
The error message will indicate the exact expected path where the .node file is looked for. Copy the build/Release/node_sqlite3.node file into that path you see in the error (which is slightly different per system) |
|
This is fixed as part of #245. I tested that the node-webkit standard build approach works in 61ac26a. This will be fixed in the upcoming [email protected] tag. |
|
This issue is still occurring for me using OS X Yosemite with Node 0.11.14 and sqlite3 1.0.8
It places the binary into: When copying the binary to the location it is being looked for in, I then get this error:
If somebody could look into this or point me in the right direction to resolving it myself, that would be awesome and much appreciated. We have a lot of code written to use this implementation so it'd be far from ideal to have to switch db implementations. (We had been using node 0.10.36 before which worked fine, but being forced to upgrade to 0.11.14 to use self signed certificates called for a new build against 0.11.14, which has resulted in the broken sqlite3). Thank you. |
|
@mattfrey - this is a very old issue. Copying is NOT recommended and the error you are seeing is because copying is not going to work. As far as your overall issue:
If you do the two above things and still hit a problem after a fresh install please create a new issue and don't comment on this old issue since its unlikely I will see it. |
STR:
I'm not entirely sure I'm doing this the way it's intended, was hoping to get some guidance. I do need to build it myself from source, though, and not pull it from github or npm.
This worked in <=v2.1.15. Only noticed it when I tried to upgrade today.