I'm getting a Node module version mismatch in a fu...
# prisma-whats-newl
lastmjs
10/19/2017, 2:18 AMI'm getting a Node module version mismatch in a function:
Copy code
Error: Module version mismatch. Expected 48, got 57.\n at Error (native)\n at Object.Module._extensions..node (module.js:597:18)lastmjs
10/19/2017, 2:19 AMI'm requiring a module that I never required before, bcrypt
lastmjs
10/19/2017, 2:19 AMI imagine bcrypt has some native code
lastmjs
10/19/2017, 2:27 AMI imagine it might have something to do with the fact that I'm running Node 8 on my machine and the function runtime is probably 6...I'm really hoping I won't have to compile my functions with Node 6 locally. Perhaps graphcool should do an npm rebuild on the target platform when functions are deployed
lastmjs
10/19/2017, 2:28 AMI imagine what's happening is that graph.cool is pushing the node_modules folder as-is...that's not good for any modules that have native code that needs to be compiled
a
agartha
10/19/2017, 7:47 AMIf you have modules that use native code (like bcrypt) and you are not running on Linux, you have to build them using Docker.
l
lastmjs
10/19/2017, 6:40 PMI'm running on Linux
a
agartha
10/19/2017, 6:45 PMI think the gyp part is only influenced by platform, not by node version
l
lastmjs
10/19/2017, 6:46 PMOkay, I'll play around
a
agartha
10/19/2017, 6:47 PMOtherwise, look at https://github.com/graphcool/serverless-image-proxy for an easy build strategy with a node 6 docker
l
lastmjs
10/21/2017, 12:00 AMI'm using Ubuntu 14, and I'm using Node 8 on my local machine. I do a graphcool deploy and I get the module version mismatch error. I then installed Node 6 on my local machine, did a fresh npm install, and did a graphcool deploy, and everything works
lastmjs
10/21/2017, 12:00 AMWhich is problematic, it shouldn't matter what version of Node I'm running ideally
lastmjs
10/21/2017, 12:00 AMWithin reason of course, but 6 versus 8
a
agartha
10/21/2017, 12:00 AMThat's where the build strategy with the Docker machine comes in.
l
lastmjs
10/21/2017, 12:01 AMIs that the final solution graph.cool would go with?
lastmjs
10/21/2017, 12:02 AMIf there is an environment that the functions need to run in, the cli should be implementing the docker solution and ensuring Node versions are identical, for a good developer experience
lastmjs
10/21/2017, 12:03 AMIs my suggestion
a
agartha
10/21/2017, 12:04 AMThat's their idea at the moment, that the CLI would do the build in the Docker
👍 1
l
lastmjs
10/21/2017, 12:05 AMIs there a GitHub issue that you know of for that?
a
agartha
10/21/2017, 12:06 AMWell, I created the exact opposite issue, so indirectly, there is one 😄 https://github.com/graphcool/graphcool/issues/795
👍 1
2 Views