-
Notifications
You must be signed in to change notification settings - Fork 31
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
Procedure not found #55
Comments
Same here. |
I got same, but got it working by downgrading to alpha.13 |
@reaby How did you downgrade it to alpha.13. The previous version works but I wasn't able to downgrade it. Npm automatically installed apha.14. Can you please tell me why? |
change your packages.json to but, i think you really should migrate to new canvas, which has prebuilt migrated already! and will work with jsdom after jsdom/jsdom#1964 gets merged! |
node --version
v8.12.0
windows x64
I get the following error. Using it in firebase functions. The same code runs on osx.
i functions: ensuring necessary APIs are enabled...
i functions: preparing functions directory for uploading...
Error: Error occurred while parsing your function triggers.
Error: The specified procedure could not be found.
\?\C:\Users\Arif\Documents\GitHub\digibaad-functions\functions\node_modules\canvas-prebuilt\canvas\build\Release\canvas.node
at Object.Module._extensions..node (module.js:682:18)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\Arif\Documents\GitHub\digibaad-functions\functions\node_modules\canvas-prebuilt\canvas\lib\bindings.js:3:18)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] deploy:
firebase deploy --only functions
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Arif\AppData\Roaming\npm-cache_logs\2018-10-06T11_26_20_352Z-debug.log
PS C:\Users\Arif\Documents\GitHub\digibaad-functions\functions>
The text was updated successfully, but these errors were encountered: