iobroker npm warn ERESOLVE overriding peer dependencynpm
-
Wo kommen die Module ohne iobroker im Pfad her?
├── canvas@2.11.2 ├── echarts@5.4.3 ├── moment@2.29.4 └── ring-client-api@12.0.1Die dürften da eigentlich nicht auftauchen, denke ich.
@thomas-braun
Wo diese herkommen, kann ich Dir beim besten willen nicht sagen. Echarts nutze ich aber und den ring-client-api auch für die Ring-Cams@thomas-braun said in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Installier den
iobroker.admin@6.17.14nochmal sauber rein.tomtaz@ioBroker:/opt/iobroker$ npm install iobroker.admin@6.17.14 npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4 npm warn Found: @iobroker/types@6.0.0 npm warn node_modules/iobroker.admin/node_modules/@iobroker/types npm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn iobroker.admin@"6.17.14" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn npm warn Conflicting peer dependency: @iobroker/types@5.0.19 npm warn node_modules/@iobroker/types npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin up to date in 4s 174 packages are looking for funding run `npm fund` for details tomtaz@ioBroker:/opt/iobroker$ -
@thomas-braun
Wo diese herkommen, kann ich Dir beim besten willen nicht sagen. Echarts nutze ich aber und den ring-client-api auch für die Ring-Cams@thomas-braun said in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Installier den
iobroker.admin@6.17.14nochmal sauber rein.tomtaz@ioBroker:/opt/iobroker$ npm install iobroker.admin@6.17.14 npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4 npm warn Found: @iobroker/types@6.0.0 npm warn node_modules/iobroker.admin/node_modules/@iobroker/types npm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn iobroker.admin@"6.17.14" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn npm warn Conflicting peer dependency: @iobroker/types@5.0.19 npm warn node_modules/@iobroker/types npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin up to date in 4s 174 packages are looking for funding run `npm fund` for details tomtaz@ioBroker:/opt/iobroker$Aber echarts muss so im tree stehen:
├── iobroker.echarts@1.7.2Das haste mal irgendwann irgendwie in das System gedübelt.
Bitte nicht direkt npm-Kommandos verwenden. Das führt nämlich unter Umständen genau zu solchen schrägen Installationen.
iob upgrade iobroker.admin@6.17.14 --omit=dev -
@thomas-braun
Wo diese herkommen, kann ich Dir beim besten willen nicht sagen. Echarts nutze ich aber und den ring-client-api auch für die Ring-Cams@thomas-braun said in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Installier den
iobroker.admin@6.17.14nochmal sauber rein.tomtaz@ioBroker:/opt/iobroker$ npm install iobroker.admin@6.17.14 npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4 npm warn Found: @iobroker/types@6.0.0 npm warn node_modules/iobroker.admin/node_modules/@iobroker/types npm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn iobroker.admin@"6.17.14" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn npm warn Conflicting peer dependency: @iobroker/types@5.0.19 npm warn node_modules/@iobroker/types npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin up to date in 4s 174 packages are looking for funding run `npm fund` for details tomtaz@ioBroker:/opt/iobroker$Neben deinem strubbeligen npm-tree kommt die Ursprungsmeldung von dem js-controller in der Alpha-Version.
Auf meinem System kommt nämlich:echad@chet:/opt/iobroker $ iob stop echad@chet:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller@next --omit=dev npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4 npm warn Found: @iobroker/types@6.0.0 npm warn node_modules/iobroker.admin/node_modules/@iobroker/types npm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn iobroker.admin@"6.17.14" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn npm warn Conflicting peer dependency: @iobroker/types@5.0.19 npm warn node_modules/@iobroker/types npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin up to date in 8s 190 packages are looking for funding run `npm fund` for details echad@chet:/opt/iobroker $ -
Neben deinem strubbeligen npm-tree kommt die Ursprungsmeldung von dem js-controller in der Alpha-Version.
Auf meinem System kommt nämlich:echad@chet:/opt/iobroker $ iob stop echad@chet:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller@next --omit=dev npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4 npm warn Found: @iobroker/types@6.0.0 npm warn node_modules/iobroker.admin/node_modules/@iobroker/types npm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn iobroker.admin@"6.17.14" from the root project npm warn npm warn Could not resolve dependency: npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin npm warn npm warn Conflicting peer dependency: @iobroker/types@5.0.19 npm warn node_modules/@iobroker/types npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4 npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-core npm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14 npm warn node_modules/iobroker.admin up to date in 8s 190 packages are looking for funding run `npm fund` for details echad@chet:/opt/iobroker $ -
@thomas-braun
Ahh ok, Danke für die Info. Dann muss es wohl von der Alpha.Bloß wie korrigiere ich nun die
├── canvas@2.11.2 ├── echarts@5.4.3 ├── moment@2.29.4 └── ring-client-api@12.0.1am besten korrigiert? Per NPM deinstallieren?
@tomtaz sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Per NPM deinstallieren?
Wenn sie auch per
npmreingedrückt worden sind ja. -
Aber echarts muss so im tree stehen:
├── iobroker.echarts@1.7.2Das haste mal irgendwann irgendwie in das System gedübelt.
Bitte nicht direkt npm-Kommandos verwenden. Das führt nämlich unter Umständen genau zu solchen schrägen Installationen.
iob upgrade iobroker.admin@6.17.14 --omit=dev@thomas-braun sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Bitte nicht direkt npm-Kommandos verwenden
schon gar nicht im falschen Verzeichnis!
@thomas-braun sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
@tomtaz sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Per NPM deinstallieren?
Wenn sie auch per
npmreingedrückt worden sind ja.aber genau dort von wo sie auch installiert wurden
-
@thomas-braun sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Bitte nicht direkt npm-Kommandos verwenden
schon gar nicht im falschen Verzeichnis!
@thomas-braun sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
@tomtaz sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
Per NPM deinstallieren?
Wenn sie auch per
npmreingedrückt worden sind ja.aber genau dort von wo sie auch installiert wurden
bei mir ist leider auch was strubbelig, zumindest bekomm ich den selben Fehler wie tomtaz.
aber npm tree schaut sauber aus!
pi4b@pi4b:~$ cd /opt/iobroker && npm ls iobroker.inst@3.0.0 /opt/iobroker ├── iobroker.adguard@0.0.8 ├── iobroker.admin@6.17.14 ├── iobroker.alarm@3.6.0 ├── iobroker.alexa2@3.26.5 ├── iobroker.alias-manager@1.2.6 ├── iobroker.backitup@3.0.5 ├── iobroker.blueconnect@0.0.5 (git+ssh://git@github.com/kopierschnitte/ioBroker .blueconnect.git#f50eada99eaffdd21802ee0cbd5bcff4fd42469d) ├── iobroker.bmw@2.8.0 ├── iobroker.bydhvs@1.5.0 ├── iobroker.daswetter@3.1.15 ├── iobroker.device-reminder@3.1.2 ├── iobroker.device-watcher@2.12.1 ├── iobroker.discovery@4.5.0 ├── iobroker.dwd@2.8.5 ├── iobroker.ecovacs-deebot@1.4.15 ├── iobroker.energiefluss-erweitert@0.4.1 (git+ssh://git@github.com/SKB-CGN/ioBr oker.energiefluss-erweitert.git#f724bf54ab9a69bc6d4533b59f560462e1bb2993) ├── iobroker.evcc@0.1.1 ├── iobroker.fritzdect@2.5.9 ├── iobroker.fronius-solarweb@0.1.0 ├── iobroker.fronius-wattpilot@4.6.3 ├── iobroker.fronius@2.1.0 ├── iobroker.ham@5.3.1 ├── iobroker.heizoel@1.0.3 ├── iobroker.ical@1.15.0 ├── iobroker.icons-mfd-svg@1.2.0 ├── iobroker.influxdb@4.0.2 ├── iobroker.intex@0.1.5 ├── iobroker.iot@3.3.0 ├── iobroker.javascript@8.6.0 ├── iobroker.js-controller@5.0.19 ├── iobroker.lovelace@4.1.10 ├── iobroker.midea@0.0.7 ├── iobroker.modbus@6.2.3 ├── iobroker.node-red@5.2.1 ├── iobroker.oilfox@4.3.0 ├── iobroker.opendtu@1.0.1 ├── iobroker.parser@2.1.0 ├── iobroker.ping@1.6.2 ├── iobroker.pushover@3.0.6 ├── iobroker.rpi2@1.3.2 ├── iobroker.shelly@7.0.0 ├── iobroker.simple-api@2.8.0 ├── iobroker.socketio@6.7.0 ├── iobroker.synology@3.1.0 ├── iobroker.telegram@3.5.3 ├── iobroker.tibberlink@3.3.1 ├── iobroker.tr-064@4.3.0 ├── iobroker.trashschedule@3.3.0 ├── iobroker.tuya@3.15.0 ├── iobroker.vis-inventwo@3.3.4 ├── iobroker.vis-materialdesign@0.5.9 ├── iobroker.vis@1.5.6 ├── iobroker.web@6.2.6 ├── iobroker.whatsapp-cmb@0.3.0 ├── iobroker.ws@2.6.1 └── iobroker.zigbee2mqtt@2.13.6 -
bei mir ist leider auch was strubbelig, zumindest bekomm ich den selben Fehler wie tomtaz.
aber npm tree schaut sauber aus!
pi4b@pi4b:~$ cd /opt/iobroker && npm ls iobroker.inst@3.0.0 /opt/iobroker ├── iobroker.adguard@0.0.8 ├── iobroker.admin@6.17.14 ├── iobroker.alarm@3.6.0 ├── iobroker.alexa2@3.26.5 ├── iobroker.alias-manager@1.2.6 ├── iobroker.backitup@3.0.5 ├── iobroker.blueconnect@0.0.5 (git+ssh://git@github.com/kopierschnitte/ioBroker .blueconnect.git#f50eada99eaffdd21802ee0cbd5bcff4fd42469d) ├── iobroker.bmw@2.8.0 ├── iobroker.bydhvs@1.5.0 ├── iobroker.daswetter@3.1.15 ├── iobroker.device-reminder@3.1.2 ├── iobroker.device-watcher@2.12.1 ├── iobroker.discovery@4.5.0 ├── iobroker.dwd@2.8.5 ├── iobroker.ecovacs-deebot@1.4.15 ├── iobroker.energiefluss-erweitert@0.4.1 (git+ssh://git@github.com/SKB-CGN/ioBr oker.energiefluss-erweitert.git#f724bf54ab9a69bc6d4533b59f560462e1bb2993) ├── iobroker.evcc@0.1.1 ├── iobroker.fritzdect@2.5.9 ├── iobroker.fronius-solarweb@0.1.0 ├── iobroker.fronius-wattpilot@4.6.3 ├── iobroker.fronius@2.1.0 ├── iobroker.ham@5.3.1 ├── iobroker.heizoel@1.0.3 ├── iobroker.ical@1.15.0 ├── iobroker.icons-mfd-svg@1.2.0 ├── iobroker.influxdb@4.0.2 ├── iobroker.intex@0.1.5 ├── iobroker.iot@3.3.0 ├── iobroker.javascript@8.6.0 ├── iobroker.js-controller@5.0.19 ├── iobroker.lovelace@4.1.10 ├── iobroker.midea@0.0.7 ├── iobroker.modbus@6.2.3 ├── iobroker.node-red@5.2.1 ├── iobroker.oilfox@4.3.0 ├── iobroker.opendtu@1.0.1 ├── iobroker.parser@2.1.0 ├── iobroker.ping@1.6.2 ├── iobroker.pushover@3.0.6 ├── iobroker.rpi2@1.3.2 ├── iobroker.shelly@7.0.0 ├── iobroker.simple-api@2.8.0 ├── iobroker.socketio@6.7.0 ├── iobroker.synology@3.1.0 ├── iobroker.telegram@3.5.3 ├── iobroker.tibberlink@3.3.1 ├── iobroker.tr-064@4.3.0 ├── iobroker.trashschedule@3.3.0 ├── iobroker.tuya@3.15.0 ├── iobroker.vis-inventwo@3.3.4 ├── iobroker.vis-materialdesign@0.5.9 ├── iobroker.vis@1.5.6 ├── iobroker.web@6.2.6 ├── iobroker.whatsapp-cmb@0.3.0 ├── iobroker.ws@2.6.1 └── iobroker.zigbee2mqtt@2.13.6Der strubbelige npm tree ist ja auch nur eine Begleiterscheinung.
Was genau wird dir in dein LogFile geschrieben? -
Der strubbelige npm tree ist ja auch nur eine Begleiterscheinung.
Was genau wird dir in dein LogFile geschrieben?$ iobroker add vis-icontwo auto --host pi4b --debug NPM version: 10.7.0 Installing iobroker.vis-icontwo@1.5.0... (System call) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4npm warn Found: @iobroker/types@6.0.0npm warn node_modules/iobroker.admin/node_modules/@iobroker/typesnpm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14npm warn node_modules/iobroker.adminnpm warn iobroker.admin@"6.17.14" from the root projectnpm warnnpm warn Could not resolve dependency:npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.admin npm warnnpm warn Conflicting peer dependency: @iobroker/types@5.0.19npm warn node_modules/@iobroker/typesnpm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.admin -
$ iobroker add vis-icontwo auto --host pi4b --debug NPM version: 10.7.0 Installing iobroker.vis-icontwo@1.5.0... (System call) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4npm warn Found: @iobroker/types@6.0.0npm warn node_modules/iobroker.admin/node_modules/@iobroker/typesnpm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14npm warn node_modules/iobroker.adminnpm warn iobroker.admin@"6.17.14" from the root projectnpm warnnpm warn Could not resolve dependency:npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.admin npm warnnpm warn Conflicting peer dependency: @iobroker/types@5.0.19npm warn node_modules/@iobroker/typesnpm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.adminInstallier den admin nochmal frisch drüber.
-
Installier den admin nochmal frisch drüber.
-
Ganz genau.
-
$ iobroker add vis-icontwo auto --host pi4b --debug NPM version: 10.7.0 Installing iobroker.vis-icontwo@1.5.0... (System call) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @iobroker/adapter-core@3.1.4npm warn Found: @iobroker/types@6.0.0npm warn node_modules/iobroker.admin/node_modules/@iobroker/typesnpm warn @iobroker/types@"6.0.0" from iobroker.admin@6.17.14npm warn node_modules/iobroker.adminnpm warn iobroker.admin@"6.17.14" from the root projectnpm warnnpm warn Could not resolve dependency:npm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.admin npm warnnpm warn Conflicting peer dependency: @iobroker/types@5.0.19npm warn node_modules/@iobroker/typesnpm warn peer @iobroker/types@"^5.0.11" from @iobroker/adapter-core@3.1.4npm warn node_modules/iobroker.admin/node_modules/@iobroker/adapter-corenpm warn @iobroker/adapter-core@"^3.1.4" from iobroker.admin@6.17.14npm warn node_modules/iobroker.admin@diamand2k22 sagte in iobroker npm warn ERESOLVE overriding peer dependencynpm:
npm warn ERESOLVE overriding peer dependency
Das liegt an der Definition der dependencies im admin (@iobroker/types sollte eine devDependency sein). PR wurde schon erstellt: https://github.com/ioBroker/ioBroker.admin/pull/2507
-
passt, danke für den Hinweis
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 Anmelden608
Online32.8k
Benutzer82.8k
Themen1.3m
Beiträge