<![CDATA[Problems updating my adapter to globals@17.4.0]]>My adapter https://github.com/Uwe1958/ioBroker.bluesound was bumped by dependabot to globals@17.4.0

Since then I get problems in the github Actions

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @iobroker/eslint-config@2.2.0
npm error Found: globals@17.4.0
npm error node_modules/globals
npm error dev globals@"^17.4.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer globals@"^16.3.0" from @iobroker/eslint-config@2.2.0
npm error node_modules/@iobroker/eslint-config
npm error dev @iobroker/eslint-config@"^2.2.0" from the root project
npm error
npm error Conflicting peer dependency: globals@16.5.0
npm error node_modules/globals
npm error peer globals@"^16.3.0" from @iobroker/eslint-config@2.2.0
npm error node_modules/@iobroker/eslint-config
npm error dev @iobroker/eslint-config@"^2.2.0" from the root project

How can this be resolved?

]]>https://forum.iobroker.net/topic/84240/problems-updating-my-adapter-to-globals@17.4.0RSS for NodeFri, 17 Apr 2026 09:11:37 GMTMon, 06 Apr 2026 17:18:46 GMT60<![CDATA[Reply to Problems updating my adapter to globals@17.4.0 on Tue, 07 Apr 2026 13:18:36 GMT]]>Generell solltest du auch keine PRs mergen bei denen die Test nicht OK sind (rotes Kreuzerl). Wenn du nicht genau weißt was du tusts bringt dir das nur zusätzliche Probleme:

375635d2-da23-45b1-bac4-df5a2eb27d93-image.jpeg

]]>https://forum.iobroker.net/post/1333406https://forum.iobroker.net/post/1333406Tue, 07 Apr 2026 13:18:36 GMT<![CDATA[Reply to Problems updating my adapter to globals@17.4.0 on Tue, 07 Apr 2026 13:16:35 GMT]]>Danke erst einmal für den Hinweis.

Leider ist aber "lint" in den Actions mit dabei. Ich habe nun folgende Dependencies eingefügt und die Actions laufen nun ohne Fehler durch. Das Problem war wohl "globals"

"devDependencies": {
    "@alcalzone/release-script": "^5.1.1",
    "@alcalzone/release-script-plugin-iobroker": "^5.1.2",
    "@alcalzone/release-script-plugin-license": "^5.1.1",
    "@alcalzone/release-script-plugin-manual-review": "^5.1.1",
    "@iobroker/adapter-dev": "^1.5.0",
    "@iobroker/testing": "^5.1.1",
    "@iobroker/eslint-config": "^2.2.0",
    "@tsconfig/node18": "^18.2.4",
    "@types/node": "^25.5.0",
    "@types/proxyquire": "^1.3.31",
    "@types/xml2js": "^0.4.14",
    "proxyquire": "^2.1.3",
    "typescript": "~6.0.2"
},
]]>https://forum.iobroker.net/post/1333405https://forum.iobroker.net/post/1333405Tue, 07 Apr 2026 13:16:35 GMT<![CDATA[Reply to Problems updating my adapter to globals@17.4.0 on Tue, 07 Apr 2026 13:15:46 GMT]]>Generell bist du mit solchen Fragen eher in unseren Entwicklungschannles auf Telegramm / Discord besser aufgehoben.
Invites findest du auf www.iobroker.dev.

]]>https://forum.iobroker.net/post/1333404https://forum.iobroker.net/post/1333404Tue, 07 Apr 2026 13:15:46 GMT<![CDATA[Reply to Problems updating my adapter to globals@17.4.0 on Tue, 07 Apr 2026 04:51:26 GMT]]>du musst den prettier geraffel wegschmeissen

und nimm dies als standard

"devDependencies": {
    "@alcalzone/release-script": "^5.1.1",
    "@alcalzone/release-script-plugin-iobroker": "^5.1.2",
    "@alcalzone/release-script-plugin-license": "^5.1.1",
    "@alcalzone/release-script-plugin-manual-review": "^5.1.1",
    "@iobroker/adapter-dev": "^1.5.0",
    "@iobroker/testing": "^5.2.2",
    "@iobroker/eslint-config": "^2.1.0",
    "@tsconfig/node14": "^14.1.8",
    "@types/node": "^25.5.0",
    "@types/node-schedule": "^2.1.8",
    "typescript": "~5.9.2"
  },
]]>https://forum.iobroker.net/post/1333336https://forum.iobroker.net/post/1333336Tue, 07 Apr 2026 04:51:26 GMT