Warnungen bei Installation js-controller
-
ioBroker läuft, aber wie bekommt man diese Warnungen weg?
npm warn deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0 npm warn deprecated swagger-methods@1.0.8: This package is no longer being maintained. npm warn deprecated string-similarity@3.0.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated superagent@7.1.6: Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated sinon@15.2.0: 16.1.1 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 har-validator@5.1.5: this library is no longer supported npm warn deprecated gauge@2.7.4: This package is no longer supported. npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported. npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. 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. (https://github.com/visionmedia/debug/issues/797) 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. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated glob@7.2.3: Glob versions prior to v9 are 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 https://v8.dev/blog/math-random for details. npm warn deprecated glob@8.1.0: Glob versions prior to v9 are 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 https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are 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. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.Die Warnung von "request" ist klar.
open Request’s Past, Present and Future #3142
open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed Update formidable #1800
-
@paul53 sagte in Warnungen bei Installation js-controller:
ioBroker läuft, aber wie bekommt man diese Warnungen weg?
Das muss in den einzelnen Adaptern, die diese Module verwenden umgestellt werden.
-
Am Beispiel von 'glob' aus meinem System:
echad@chet:/opt/iobroker $ npm ls glob iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.admin@7.2.1 │ └─┬ archiver@7.0.1 │ └─┬ archiver-utils@5.0.2 │ └── glob@10.3.12 ├─┬ iobroker.ankersolix2@0.0.2-alpha.0 (git+ssh://git@github.com/ronny130286/ioBroker.ankersolix2.git#80fb5950f7fd33c55cf8595cd128c6c564875f25) │ └─┬ async-mqtt@2.6.3 │ └─┬ mqtt@4.3.8 │ └─┬ help-me@3.0.0 │ └── glob@7.2.3 ├─┬ iobroker.ble@0.14.0 │ └─┬ @abandonware/noble@1.9.2-25 │ └─┬ @abandonware/bluetooth-hci-socket@0.5.3-12 │ └─┬ node-gyp@10.1.0 │ ├── glob@10.3.12 deduped │ └─┬ make-fetch-happen@13.0.1 │ └─┬ cacache@18.0.3 │ └── glob@10.3.12 deduped ├─┬ iobroker.echarts@1.9.2 │ └─┬ canvas@2.11.2 │ └─┬ @mapbox/node-pre-gyp@1.0.11 │ └─┬ rimraf@3.0.2 │ └── glob@7.2.3 ├─┬ iobroker.govee-app@0.0.6 (git+ssh://git@github.com/TA2k/ioBroker.govee-app.git#6a0f84cfb34eb3a0ca647c7a519b9d5a48ccfb85) │ └─┬ aws-iot-device-sdk@2.2.15 │ └─┬ mqtt@4.2.8 │ └─┬ help-me@3.0.0 │ └── glob@7.2.3 ├─┬ iobroker.sainlogic@0.11.4 │ └─┬ jshint@2.13.6 │ └─┬ cli@1.0.1 │ └── glob@7.2.3 ├─┬ iobroker.simple-api@2.8.0 │ └─┬ @iobroker/testing@4.1.3 │ └─┬ mocha@10.4.0 │ └── glob@8.1.0 └─┬ iobroker.tuya@3.16.0 └─┬ mqtt@4.3.8 └─┬ help-me@3.0.0 └── glob@7.2.3 echad@chet:/opt/iobroker $
