You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> npm start
> node-red-bluemix-starter@0.8.0 start R:\Downloads\node-red-bluemix-starter-master
> node --max-old-space-size=160 index.js --settings ./bluemix-settings.js -v
15 Aug 16:19:19 - Starting Node-RED on IBM Cloud bootstrap
15 Aug 16:19:19 - Loading bluemix-settings.js
15 Aug 16:19:19 - Failed to find Cloudant service: /^node-red-bluemix-starter.cloudantNoSQLDB/
15 Aug 16:19:20 - Loading application settings
R:\Downloads\node-red-bluemix-starter-master\node_modules\node-red\red\runtime\storage\localfilesystem\projects\index.js:45
log = runtime.log;
^
TypeError: Cannot read property 'log' of undefined
at Object.init (R:\Downloads\node-red-bluemix-starter-master\node_modules\node-red\red\runtime\storage\localfilesystem\projects\index.js:45:19)
at Object.init (R:\Downloads\node-red-bluemix-starter-master\node_modules\node-red\red\runtime\storage\localfilesystem\index.js:62:32)
at Object.<anonymous> (R:\Downloads\node-red-bluemix-starter-master\index.js:36:13)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-bluemix-starter@0.8.0 start: `node --max-old-space-size=160 index.js --settings ./bluemix-settings.js -v`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-bluemix-starter@0.8.0 start 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! D:\Users\rophy\npm-cache\_logs\2018-08-15T08_19_20_549Z-debug.log
version: 0.8.0
Fix: in
index.js36:
:Change the line to:
Seems to make the error gone, but I'm not sure if it is the right thing to do.
The text was updated successfully, but these errors were encountered: