@Shane Dzartov Thanks, From the logs you've shared, it seems that the version of Node.js you have installed is not supported by the package. The package requires Node.js version 14.x, You can try installing a supported version of Node.js and then try installing the botframework-cli package again.
Error when trying to install BotFrameWork CLI
Hi,
I'm trying to install the botframework-cli as per: https://learn.microsoft.com/en-us/composer/how-to-create-custom-actions#merge-schema-files
My logs from the terminal are as below:
C:\Users\shane>npm i -g @microsoft/botframework-cli
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@microsoft/bf-orchestrator-cli@4.15.0',
npm WARN EBADENGINE required: { node: '^10.0.0 || ^12.0.0 || ^13.0.0 || ^14.0.0' },
npm WARN EBADENGINE current: { node: 'v20.0.0', npm: '9.6.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@microsoft/bf-orchestrator@4.15.0',
npm WARN EBADENGINE required: { node: '^10.0.0 || ^12.0.0 || ^13.0.0 || ^14.0.0' },
npm WARN EBADENGINE current: { node: 'v20.0.0', npm: '9.6.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@microsoft/orchestrator-core@4.14.4',
npm WARN EBADENGINE required: { node: '^10.0.0 || ^12.0.0 || ^13.0.0 || ^14.0.0 || ^16.0.0' },
npm WARN EBADENGINE current: { node: 'v20.0.0', npm: '9.6.4' }
npm WARN EBADENGINE }
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated @oclif/screen@1.0.4: Deprecated in favor of @oclif/core
npm WARN deprecated cli-ux@4.9.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated cli-ux@5.3.3: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated cli-ux@5.6.7: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup [
npm WARN cleanup 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules\node-gyp'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli\node_modules\node-gyp'
npm WARN cleanup }
npm WARN cleanup ],
npm WARN cleanup [
npm WARN cleanup 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli\node_modules',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@microsoft\bf-dispatcher\lib\model\supervised\classifier'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli\node_modules\@microsoft\bf-dispatcher\lib\model\supervised\classifier'
npm WARN cleanup }
npm WARN cleanup ],
npm WARN cleanup [
npm WARN cleanup 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@microsoft\bf-orchestrator-cli\node_modules@oclif\config'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli\node_modules\@microsoft\bf-orchestrator-cli\node_modules\@oclif\config'
npm WARN cleanup }
npm WARN cleanup ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@microsoft\orchestrator-core
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node-pre-gyp install
npm ERR! response status 404 Not Found on https://bcmodelsprod.azureedge.net/native/orchestrator-core-v4.14.4-node-v115-win32-ia32.tar.gz
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@1.0.10
npm ERR! node-pre-gyp info using node@20.0.0 | win32 | ia32
npm ERR! node-pre-gyp info check checked for "C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@microsoft\orchestrator-core\orchestrator-core.node" (not found)
npm ERR! node-pre-gyp http GET https://bcmodelsprod.azureedge.net/native/orchestrator-core-v4.14.4-node-v115-win32-ia32.tar.gz
npm ERR! node-pre-gyp ERR! install response status 404 Not Found on https://bcmodelsprod.azureedge.net/native/orchestrator-core-v4.14.4-node-v115-win32-ia32.tar.gz
npm ERR! node-pre-gyp ERR! install error
npm ERR! node-pre-gyp ERR! stack Error: response status 404 Not Found on https://bcmodelsprod.azureedge.net/native/orchestrator-core-v4.14.4-node-v115-win32-ia32.tar.gz
npm ERR! node-pre-gyp ERR! stack at C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@mapbox\node-pre-gyp\lib\install.js:67:15
npm ERR! node-pre-gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
npm ERR! node-pre-gyp ERR! System Windows_NT 10.0.19044
npm ERR! node-pre-gyp ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Users\shane\AppData\Roaming\npm\node_modules\@microsoft\botframework-cli\node_modules\@mapbox\node-pre-gyp\bin\node-pre-gyp" "install"
npm ERR! node-pre-gyp ERR! cwd C:\Users\shane\AppData\Roaming\npm\node_modules@microsoft\botframework-cli\node_modules@microsoft\orchestrator-core
npm ERR! node-pre-gyp ERR! node -v v20.0.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.10
npm ERR! node-pre-gyp ERR! not ok
npm ERR! A complete log of this run can be found in: C:\Users\shane\AppData\Local\npm-cache_logs\2023-04-26T12_07_30_235Z-debug-0.log
Any advice? It seems that the modern versions of NODE and npm don't support the CLI?