-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Sharp build with wrong NODE_MODULE_VERSION when deploying using meteor-up #1374
Comments
Hello, the |
I understand that. But since Node 4 is not installed both in Dev & Prod as indicated, do you think it can come from any of the sharp dependencies ? I checked for any forgotten installation of Node 4 pretty much anywhere I could think of (there is a great reminder by the way on how to completely remove node.js from Windows). The only Node version installed on my dev environment is the 8.11.4. I also removed the node-modules/sharp/vendor folder before pushing to production. |
I got it working by pushing from a MacOSX dev environment. Sharp is then compiled with the right NODE_VERSION on the production server. I'm clueless on how to resolve this issue on Windows and why there is a difference. @lovell If that's ok, I'd like to keep this issue open just in case something new comes up ? Thank you for your reponse. |
What is the output when |
Feel free to re-open with more information if this problem remains. |
|
Hi guys ! First of all, thank you for this package and for all your work in the issues section, it has been a great help.
Context
I'm trying to deploy my meteor project on production using [zodern/meteor-up].(https://github.com/zodern/meteor-up).
Dev :
Windows 10 (x64)
meteor 1.7.0.5
meteor-up 1.4.5
node v8.11.4 (only one version installed)
Prod :
Docker instance (abernix/meteord:node-8.11.2-base image) running on Debian 9
node v8.11.2
Build
During build sharp is not detecting any global installation of libvips and get the pre-compiled binaries from the github repo.
Error
Everything looks successfull until meteor starts. Then this error occurs:
I tried a lot a different approaches during these past two days without success.
Do you guys have any ideas ?
The text was updated successfully, but these errors were encountered: