Whilst evaluating KUIB, I appear to have successfully created a set of Progress Data Objects (OE11.7.3) and an example app in the ui builder (Version: 3.0.0.190 Trial) to consume those services. But when I try to generate or start, the UI builder shows a message titled "App Generation" with detail "We are installing node packages, it might take a few minutes..." which never completes. Even after a few hours the message remains.
Has anyone experienced this? Any suggestions how to resolve this issue greatly appreciated.
Regards
3 Answers, 1 is accepted
Thank you for your interest in Kendo UI Builder!
We've identified that we need to improve that window of installing node modules - we will add more information to it so it is clear what is going on.
There might be a problem with npm on your side, slow internet or even a slow disk. Could you please open a support ticket and send us your log at %appdata%\KendoUIBuilder\KUIBLog.log? The log file has the necessary information to identify the issue.
The workaround is to open a command prompt, navigate to <your-project-folder>\app and run `npm install` manually. If the node_modules folder exists we won't try to install your modules and Generate will only Generate your app.
If you have any other questions, please, don't hesitate to write back.
Regards,
Svetlozar
Progress Telerik
Rank 1
Thank you for the very prompt reply. Looking at the log file you highlight, it shows...
[4:51:37 PM] INFO 'npm' is not recognized as an internal or external command,
operable program or batch file.
[4:51:37 PM] INFO Installation of node modules has failed! { Error: spawn npm ENOENT
at notFoundError (C:\Program Files (x86)\Progress\Kendo UI Builder R2 2018\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:11:11)
at verifyENOENT (C:\Program Files (x86)\Progress\Kendo UI Builder R2 2018\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:46:16)
at ChildProcess.cp.emit (C:\Program Files (x86)\Progress\Kendo UI Builder R2 2018\resources\app.asar\node_modules\cross-spawn\lib\enoent.js:33:19)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) errno: 'ENOENT', code: 'ENOENT', syscall: 'spawn npm' }
Given your recommendation to run npm manually results in the same error, I assume npm is either missing or not in the path. How does npm get installed?
Regards,
Marcus
npm is installed as part of the NodeJS distribution. If you have installed NodeJS you should have npm as well, so I assume you just don't have it in the PATH. npm.cmd is right next to node.exe and it should be in C:\Program Files\nodejs\ or (Program Files x86).
Let me know if you have managed to resolve the issue.
Regards,
Svetlozar
Progress Telerik