Error when Build Bahmni EMR UI

Development
1

Hello Team,

I am following this tutorial ( https://bahmni.atlassian.net/wiki/display/BAH/Setting+up+Bahmni+Dev+Environment) to setup development enviroment for bahmni but when i try to build EMR Ui it fail, i have included nbm debug file npm-debug.txt (580.2 KB)

Thank you

2

Hi @ian,

Which version of npm are you using? You can follow a previous post and see if it fixes the problem. fsevents error Windows 10

3

Hi Venkata I am using v 0.86

4

Try running npm install -g npm@3.10.7 and then do npm install.

5

Hello Venkata

i run that commands but this is the error am getting now

npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.15 npm ERR! Windows_NT 10.0.14393 npm ERR! argv ā€œC:\Program Files\nodejs\node.exeā€ ā€œC:\Users\ucc-ian\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.jsā€ ā€œinstallā€ npm ERR! node v6.9.2 npm ERR! npm v3.10.7 npm ERR! code ELIFECYCLE

npm ERR! fsevents@1.0.14 install: node-pre-gyp install --fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the fsevents@1.0.14 install script ā€˜node-pre-gyp install --fallback-to-buildā€™. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the fsevents package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs fsevents npm ERR! Or if that isnā€™t available, you can get their info via: npm ERR! npm owner ls fsevents npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\bahmi\bahmni-vagrant\openmrs-module-bahmniapps\ui\npm-debug.log npm ERR! code 1

Thank you

6

Could you please run npm install --no-optional ? fsevents is an optional dependency. But, because of some issue with npm, it is failing.

7

Thank you it worked

1 Like
8

Cool, thatā€™s nice to hear.