This repository has been archived by the owner on May 15, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 115
Not working with latest stable version of node #110
Labels
Comments
You must have installed the emulator, then upgraded node, then tried to start the emulator. To fix:
|
OK I uninstalled (npm uninstall -g @google-cloud/functions-emulator) and reinstalled. Here's what I get now when I run the functions deploy command mentioned in the Google Actions tutorial (https://developers.google.com/actions/get-started/deploy-fulfillment):
|
Hi @stevebingsoo can you try again (referencing Installing the Emulator) and let me know how it goes? I recommend doing:
|
I get the same problem,
I'm using Node v6.9.1 as mentioned. Can you help me fixing this. |
I'm pushing 1.0.0-alpha.21 which should hopefully fix this issue, and at the least reveal what may have been causing it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Warning: You're using Node.js v7.10.0 but Google Cloud Functions only supports v6.9.1.
Error: The module '/usr/local/lib/node_modules/@google-cloud/functions-emulator/node_modules/grpc/src/node/extension_binary/grpc_node.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 47. This version of Node.js requires
NODE_MODULE_VERSION 51. Please try re-compiling or re-installing
the module (for instance, using
npm rebuild
ornpm install
).at Object.Module._extensions..node (module.js:598:18)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/usr/local/lib/node_modules/@google-cloud/functions-emulator/node_modules/grpc/src/node/src/grpc_extension.js:38:15)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
Steps to reproduce
functions start
Thanks!
The text was updated successfully, but these errors were encountered: