-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: Could not locate the bindings file." #76
Comments
Yeah I run into this with every upgrade too. We need to find some way to link to one of these issues about it/documentation around it. |
@rgbkrk Perhaps we should open an issue at the npm repository. Ideally, when node changes, we'd like npm to recompile all the native modules. |
@n-riesco What if ijavascript added an npm postinstall script that runs |
Would you be able to check whether adding |
I use the n package to switch between versions of Node. To reproduce:
To fix, either:
Again, adding an npm postinstall script that runs Known issues
Lastly, zmq is the culprit here because it's zmq's native modules that need to be rebuilt, so removing the dependency on zmq's native modules would resolve this issue and I believe this is something that @rgbkrk has been working on... |
@gnestor The error message you get now is different. The original error message in this issue was @rgbkrk What error message do you get in your case? An |
@n-riesco You're right! I had an older version of ijavascript installed (probably 1 year old) and I ran One issue with instructing users to run |
This makes me wonder if having an ijs --upgrade option would allow us to do it intelligently. That or we rebuild on start up. Both of these may be silly ideas though. I'm an nvm user, so the messages are quite similar to n. Sometimes the entire directory for an old version gets nuked by me, and it's the version that was mapped in the kernel spec. I'm used to dealing with native module and upgrades so I just install all over again (unlike a global node install). |
I've opened an issue in the |
Moved back from n-riesco/jmp#15 |
After the experience gained with n-riesco/jp-babel@2c7227c I'm convinced this rebuild issue shouldn't be handled by a package itself, because the package would have to know about the environment were it has been installed (is it plain For this reason, I'm going to close this issue. |
I ran into this issue and solved by uninstalling and reinstalling ijavascript globally. It probably was related to the initial installation being installed with Node < 6 and an update being installed with Node 6.
The text was updated successfully, but these errors were encountered: