Fehler bei Update von vis-icontwo 2.11.6
-
npm fund ist uninteressant.
Wie schaut der Baum denn nun nach dem prune aus?@Thomas-Braun
hi, siehe #17juergen@iobroker:/opt/iobroker$ cd /opt/iobroker && npm prune npm warn deprecated npmlog@4.1.2: This package is no longer supported. npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are 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: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me npm warn deprecated gauge@2.7.4: This package is no longer supported. up to date in 3s 214 packages are looking for funding run `npm fund` for details -
@Thomas-Braun
hi, siehe #17juergen@iobroker:/opt/iobroker$ cd /opt/iobroker && npm prune npm warn deprecated npmlog@4.1.2: This package is no longer supported. npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are 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: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me npm warn deprecated gauge@2.7.4: This package is no longer supported. up to date in 3s 214 packages are looking for funding run `npm fund` for details -
cd /opt/iobroker && npm ls
sind nicht wegjuergen@iobroker:/opt/iobroker$ cd /opt/iobroker && npm ls [sudo] password for juergen: iobroker.inst@3.0.0 /opt/iobroker ├── @stoprocent/bluetooth-hci-socket@1.5.2 extraneous ├── @types/w3c-web-usb@1.0.13 extraneous ├── @yarnpkg/lockfile@1.1.0 extraneous ├── find-yarn-workspace-root@2.0.0 extraneous ├── iobroker.admin@7.8.23 ├── iobroker.backitup@3.3.17 ├── iobroker.birthdays@5.0.0 ├── iobroker.daswetter@4.5.3 ├── iobroker.device-reminder@3.1.2 ├── iobroker.discovery@5.0.0 ├── iobroker.dwd@2.8.5 ├── iobroker.echarts@3.1.0 ├── iobroker.email@2.0.4 ├── iobroker.energiefluss@3.6.2 ├── iobroker.fb-checkpresence@1.4.2 ├── iobroker.feiertage@1.4.0 ├── iobroker.flot@1.12.0 ├── iobroker.fritzbox@0.7.0 ├── iobroker.fritzdect@2.6.2 ├── iobroker.fullcalendar@2.4.5 ├── iobroker.history@4.0.0 ├── iobroker.hm-rega@5.1.0 ├── iobroker.hm-rpc@3.0.1 ├── iobroker.ical@1.20.1 ├── iobroker.icons-fatcow-hosting@0.1.0 ├── iobroker.icons-icons8@0.0.1 ├── iobroker.icons-material-png@0.1.0 ├── iobroker.icons-mfd-png@1.2.1 ├── iobroker.icons-mfd-svg@1.2.0 ├── iobroker.icons-open-icon-library-png@0.1.2 ├── iobroker.influxdb@4.0.2 ├── iobroker.javascript@9.0.18 ├── iobroker.js-controller@7.2.2 ├── iobroker.melcloud@3.0.4 ├── iobroker.mqtt@6.1.4 ├── iobroker.node-red@6.0.7 ├── iobroker.proxmox@2.6.1 ├── iobroker.pvforecast@6.1.0 ├── iobroker.radar2@2.4.0 ├── iobroker.sayit@5.1.0 ├── iobroker.scenes@4.0.4 ├── iobroker.shelly@10.6.1 ├── iobroker.shuttercontrol@2.0.12 ├── iobroker.simple-api@3.0.7 ├── iobroker.snmp@3.4.0 ├── iobroker.socketio@7.1.3 ├── iobroker.sonoff@3.3.0 ├── iobroker.sonos@3.0.0 ├── iobroker.synology@3.1.0 ├── iobroker.systeminfo@1.3.0 ├── iobroker.tankerkoenig@3.4.0 ├── iobroker.telegram@4.1.0 ├── iobroker.text2command@4.0.0 ├── iobroker.tr-064@4.3.0 ├── iobroker.upnp@1.1.0 ├── iobroker.vis-bars@0.1.4 ├── iobroker.vis-canvas-gauges@1.0.1 ├── iobroker.vis-history@1.0.0 ├── iobroker.vis-hqwidgets@1.6.1 ├── iobroker.vis-icontwo@2.11.6 ├── iobroker.vis-inventwo@4.1.1 ├── iobroker.vis-jqui-mfd@1.1.3 ├── iobroker.vis-justgage@2.1.7 ├── iobroker.vis-material-advanced@1.7.4 ├── iobroker.vis-material@0.2.0 ├── iobroker.vis-materialdesign@0.5.9 ├── iobroker.vis-metro@1.2.0 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-timeandweather@1.2.2 ├── iobroker.vis-weather@2.5.13 ├── iobroker.vis@1.5.6 ├── iobroker.web@8.0.0 ├── iobroker.whatsapp-cmb@0.3.0 ├── iobroker.ws@4.1.0 ├── is-docker@2.2.1 extraneous ├── is-wsl@2.2.0 extraneous ├── json-stable-stringify@1.3.0 extraneous ├── jsonify@0.0.1 extraneous ├── klaw-sync@6.0.0 extraneous ├── micromatch@4.0.8 extraneous ├── node-gyp-build@4.8.4 extraneous ├── open@7.4.2 extraneous ├── patch-package@8.0.1 extraneous ├── slash@2.0.0 extraneous ├── tmp@0.2.5 extraneous ├── usb@2.17.0 extraneous └── yaml@2.8.2 extraneous -
cd /opt/iobroker && npm ls
sind nicht wegjuergen@iobroker:/opt/iobroker$ cd /opt/iobroker && npm ls [sudo] password for juergen: iobroker.inst@3.0.0 /opt/iobroker ├── @stoprocent/bluetooth-hci-socket@1.5.2 extraneous ├── @types/w3c-web-usb@1.0.13 extraneous ├── @yarnpkg/lockfile@1.1.0 extraneous ├── find-yarn-workspace-root@2.0.0 extraneous ├── iobroker.admin@7.8.23 ├── iobroker.backitup@3.3.17 ├── iobroker.birthdays@5.0.0 ├── iobroker.daswetter@4.5.3 ├── iobroker.device-reminder@3.1.2 ├── iobroker.discovery@5.0.0 ├── iobroker.dwd@2.8.5 ├── iobroker.echarts@3.1.0 ├── iobroker.email@2.0.4 ├── iobroker.energiefluss@3.6.2 ├── iobroker.fb-checkpresence@1.4.2 ├── iobroker.feiertage@1.4.0 ├── iobroker.flot@1.12.0 ├── iobroker.fritzbox@0.7.0 ├── iobroker.fritzdect@2.6.2 ├── iobroker.fullcalendar@2.4.5 ├── iobroker.history@4.0.0 ├── iobroker.hm-rega@5.1.0 ├── iobroker.hm-rpc@3.0.1 ├── iobroker.ical@1.20.1 ├── iobroker.icons-fatcow-hosting@0.1.0 ├── iobroker.icons-icons8@0.0.1 ├── iobroker.icons-material-png@0.1.0 ├── iobroker.icons-mfd-png@1.2.1 ├── iobroker.icons-mfd-svg@1.2.0 ├── iobroker.icons-open-icon-library-png@0.1.2 ├── iobroker.influxdb@4.0.2 ├── iobroker.javascript@9.0.18 ├── iobroker.js-controller@7.2.2 ├── iobroker.melcloud@3.0.4 ├── iobroker.mqtt@6.1.4 ├── iobroker.node-red@6.0.7 ├── iobroker.proxmox@2.6.1 ├── iobroker.pvforecast@6.1.0 ├── iobroker.radar2@2.4.0 ├── iobroker.sayit@5.1.0 ├── iobroker.scenes@4.0.4 ├── iobroker.shelly@10.6.1 ├── iobroker.shuttercontrol@2.0.12 ├── iobroker.simple-api@3.0.7 ├── iobroker.snmp@3.4.0 ├── iobroker.socketio@7.1.3 ├── iobroker.sonoff@3.3.0 ├── iobroker.sonos@3.0.0 ├── iobroker.synology@3.1.0 ├── iobroker.systeminfo@1.3.0 ├── iobroker.tankerkoenig@3.4.0 ├── iobroker.telegram@4.1.0 ├── iobroker.text2command@4.0.0 ├── iobroker.tr-064@4.3.0 ├── iobroker.upnp@1.1.0 ├── iobroker.vis-bars@0.1.4 ├── iobroker.vis-canvas-gauges@1.0.1 ├── iobroker.vis-history@1.0.0 ├── iobroker.vis-hqwidgets@1.6.1 ├── iobroker.vis-icontwo@2.11.6 ├── iobroker.vis-inventwo@4.1.1 ├── iobroker.vis-jqui-mfd@1.1.3 ├── iobroker.vis-justgage@2.1.7 ├── iobroker.vis-material-advanced@1.7.4 ├── iobroker.vis-material@0.2.0 ├── iobroker.vis-materialdesign@0.5.9 ├── iobroker.vis-metro@1.2.0 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-timeandweather@1.2.2 ├── iobroker.vis-weather@2.5.13 ├── iobroker.vis@1.5.6 ├── iobroker.web@8.0.0 ├── iobroker.whatsapp-cmb@0.3.0 ├── iobroker.ws@4.1.0 ├── is-docker@2.2.1 extraneous ├── is-wsl@2.2.0 extraneous ├── json-stable-stringify@1.3.0 extraneous ├── jsonify@0.0.1 extraneous ├── klaw-sync@6.0.0 extraneous ├── micromatch@4.0.8 extraneous ├── node-gyp-build@4.8.4 extraneous ├── open@7.4.2 extraneous ├── patch-package@8.0.1 extraneous ├── slash@2.0.0 extraneous ├── tmp@0.2.5 extraneous ├── usb@2.17.0 extraneous └── yaml@2.8.2 extraneous@Alero Also noch Chaos drin.
Ich weiß aber nicht wo da der Hase im Pfeffer liegt. -
was ist wenn ich die pakete von hand deinstalliere?
z.B. npm uninstall json-stable-stringify -
cd /opt/iobroker && npm ls slash
juergen@iobroker:~$ cd /opt/iobroker && npm ls slash [sudo] password for juergen: iobroker.inst@3.0.0 /opt/iobroker ├─┬ patch-package@8.0.1 extraneous │ └── slash@2.0.0 deduped └── slash@2.0.0 extraneous -
cd /opt/iobroker && npm ls slash
juergen@iobroker:~$ cd /opt/iobroker && npm ls slash [sudo] password for juergen: iobroker.inst@3.0.0 /opt/iobroker ├─┬ patch-package@8.0.1 extraneous │ └── slash@2.0.0 deduped └── slash@2.0.0 extraneousIch würde behaupten, das braucht keiner mehr.
Aber wie hast du die Dinger überhaupt in das System reingehievt? Unorthodoxe Installation von irgendwas via github oder direkt per npm? -
Mit einem
npm uninstall PAKETNAMEin dem entsprechenden Verzeichnis.
Kann aber sein, dass du dir damit dann andere Baustellen aufreißt. -
was ist mit dem Befahl yarn? wenn ich ihn nutzen will muss ich ihn erst installieren, oder?
Wenn das Paket weiterhin als extraneous oder Warnung auftaucht, nutzen Sie den Aufräum-Befehl von Yarn, um veraltete oder ungenutzte Verknüpfungen zu entfernen:yarn cache clean yarn clean -
So tief stecke ich in yarn und npm nicht drin.
Aber ganz grundsätzlich ist --force und 'wildes' Löschen von Dingen im npm tree mit Vorsicht zu genießen. -
Bein reboot kommt im Protokoll u.a. folgendes:
iobroker npm-install: npm error code 7npm error path /opt/iobroker/node_modules/opengpionpm error command failednpm error command sh -c node-gyp rebuildnpm error (node:887) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.npm error (Use `node --trace-deprecation ...` to show where the warning was created)npm error gyp ERR! UNCAUGHT EXCEPTION npm error gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#<Object>'npm error gyp ERR! stack at createConfigFile (/opt/iobroker/node_modules/node-gyp/lib/configure.js:117:21)npm error gyp ERR! stack at /opt/iobroker/node_modules/node-gyp/lib/configure.js:84:9npm error gyp ERR! stack at FSReqCallback.oncomplete (node:fs:186:23)npm error gyp ERR! System Linux 6.12.63+deb13-amd64npm error gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"npm error gyp ERR! cwd /opt/iobroker/node_modules/opengpionpm error gyp ERR! node -v v22.23.1npm error gyp ERR! node-gyp -v v7.1.2npm error gyp ERR! Node-gyp failed to build your package.npm error gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2026-07-03T09_14_17_962Z-debug-0.loghost.iobroker Cannot install iobroker.rpi2@2.4.0: 7
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden433
Online33.0k
Benutzer83.4k
Themen1.3m
Beiträge