Hello all,
I am facing an issue while installing the edge impulse CLI. I have python 3.9.0, VS 2019 and Node.js 20.16.0 versions. I am not sure what is the issue here. And here I tried command prompt as administrator still Edge Impulse CLI is not installing. Can anyone please help me.
CMD errors:
C:\Users\BARRPRA>npm install -g edge-impulse-cli --force
npm warn using --force Recommended protections disabled.
npm warn deprecated osenv@0.1.5: This package is no longer supported.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated move-concurrently@1.0.1: This package is no longer supported.
npm warn deprecated @zeit/dockerignore@0.0.5: “@zeit/dockerignore” is no longer maintained
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated figgy-pudding@3.5.2: This module is no longer supported.
npm warn deprecated copy-concurrently@1.0.5: This package is no longer supported.
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated request-promise@4.2.4: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub)
npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (ReDos Vulnerability Regression Visibility Notice · Issue #797 · debug-js/debug · GitHub)
npm warn deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported.
npm warn deprecated gauge@2.7.4: This package is no longer supported.
npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm warn deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated fstream@1.0.12: This package is no longer supported.
npm warn cleanup Failed to remove some directories [
npm warn cleanup [
npm warn cleanup ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\encoding’,
npm warn cleanup [Error: EPERM: operation not permitted, rmdir ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\encoding\node_modules’] {
npm warn cleanup errno: -4048,
npm warn cleanup code: ‘EPERM’,
npm warn cleanup syscall: ‘rmdir’,
npm warn cleanup path: ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\encoding\node_modules’
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli’,
npm warn cleanup [Error: EPERM: operation not permitted, rmdir ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-fs’] {
npm warn cleanup errno: -4048,
npm warn cleanup code: ‘EPERM’,
npm warn cleanup syscall: ‘rmdir’,
npm warn cleanup path: ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-fs’
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules’,
npm warn cleanup [Error: EPERM: operation not permitted, rmdir ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-stream\node_modules\readable-stream\lib’] {
npm warn cleanup errno: -4048,
npm warn cleanup code: ‘EPERM’,
npm warn cleanup syscall: ‘rmdir’,
npm warn cleanup path: ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-stream\node_modules\readable-stream\lib’
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli’,
npm warn cleanup [Error: EPERM: operation not permitted, rmdir ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-stream\node_modules\readable-stream’] {
npm warn cleanup errno: -4048,
npm warn cleanup code: ‘EPERM’,
npm warn cleanup syscall: ‘rmdir’,
npm warn cleanup path: ‘C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules\tar-stream\node_modules\readable-stream’
npm warn cleanup }
npm warn cleanup ]
npm warn cleanup ]
npm error code 1
npm error path C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
npm error gyp info it worked if it ends with ok
npm error gyp info using node-gyp@10.1.0
npm error gyp info using node@20.16.0 | win32 | x64
npm error gyp info find Python using Python version 3.9.0 found at “C:\Users\BARRPRA\AppData\Local\Programs\Python\Python39\python.exe”
npm error gyp http GET https://nodejs.org/download/release/v20.16.0/node-v20.16.0-headers.tar.gz
npm error gyp http fetch GET https://nodejs.org/download/release/v20.16.0/node-v20.16.0-headers.tar.gz attempt 1 failed with SELF_SIGNED_CERT_IN_CHAIN
npm error gyp WARN install got an error, rolling back install
npm error gyp ERR! configure error
npm error gyp ERR! stack FetchError: request to https://nodejs.org/download/release/v20.16.0/node-v20.16.0-headers.tar.gz failed, reason: self-signed certificate in certificate chain
npm error gyp ERR! stack at ClientRequest. (C:\Program Files\nodejs\node_modules\npm\node_modules\minipass-fetch\lib\index.js:130:14)
npm error gyp ERR! stack at ClientRequest.emit (node:events:519:28)
npm error gyp ERR! stack at _destroy (node:_http_client:880:13)
npm error gyp ERR! stack at onSocketNT (node:_http_client:900:5)
npm error gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
npm error gyp ERR! System Windows_NT 10.0.19045
npm error gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js” “rebuild”
npm error gyp ERR! cwd C:\Users\BARRPRA\AppData\Roaming\npm\node_modules\edge-impulse-cli\node_modules@serialport\bindings
npm error gyp ERR! node -v v20.16.0
npm error gyp ERR! node-gyp -v v10.1.0
npm error gyp ERR! not ok
Thank you for your attention!
Best Regards,
Prasanna VIshnu.