Application won't start after issuing npm start. It produces error

[vadiraj-joshi]

Hi,

I followed all the steps and configured services. Upon trying to run "npm start" it gives following errors. Please help

C:\My Projects\Watson\Sand\watson-multimedia-analyzer>npm start

watson-multimedia-analyzer@0.0.6 start C:\My Projects\Watson\Sand\watson-multimedia-analyzer
node app.js | node_modules/.bin/pino

'node_modules' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v4.5.0
npm ERR! npm v2.15.9
npm ERR! code ELIFECYCLE
npm ERR! watson-multimedia-analyzer@0.0.6 start: node app.js | node_modules/.bin/pino
npm ERR! Exit status 255
npm ERR!
npm ERR! Failed at the watson-multimedia-analyzer@0.0.6 start script 'node app.js | node_modules/.bin/pino '.
npm ERR! This is most likely a problem with the watson-multimedia-analyzer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node app.js | node_modules/.bin/pino
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs watson-multimedia-analyzer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls watson-multimedia-analyzer
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! C:\My Projects\Watson\Sand\watson-multimedia-analyzer\npm-debug.log

Thanks,
Vadiraj

[rhagarty]

@vadiraj-joshi - you can try removing the pipe in the start command.

But there is a bigger issue. This code pattern has known issues when using new instances of Visual Recognition that require IAM api keys. There are also some API changes in newest version of the SDK that break the way we process images.

No time table yet on when we will fix this.

[dolph]

cc- @sanjeevghimire

[SwethaPatlola123]

@vadiraj-joshi : I am facing similar issue. Were you able to fix it? Thanks