Neues YouTube-Video: Visualisierung im Devices-Adapter

[omega235]

Hallo,

ich habe einen Adapter (https://github.com/Omega236/ioBroker.virtualpowermeter) der vor einer Woche mit travis-ci noch OK lief, jetzt laufen alle nodejs 8.x tests auf Fehler (https://travis-ci.org/github/Omega236/ioBroker.virtualpowermeter):

 iobroker.js-controller@3.0.8 install /tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller
> node iobroker.js setup first
creating conf/iobroker.json
object 0_userdata.0.example_state created
object 0_userdata.0 created
object alias.0 created
object system.certificates created
object system.repositories created
object system.config created
object enum.functions created
object enum.rooms created
object system.group.user created
object system.group.administrator created
object _design/system created
object system.meta.uuid created: 3ddff591-8b31-5dd3-d63f-4bd02962ad89
object system.user.admin created
/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/objects/objectsInMemFileDB.js:1854
            !isDeepStrictEqual(obj.common.defaultNewAcl, this.dataset[id].common.defaultNewAcl)) {
             ^
TypeError: isDeepStrictEqual is not a function
    at ObjectsInMemoryServer._setObject (/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/objects/objectsInMemFileDB.js:1854:14)
    at utils.checkObjectRights (/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/objects/objectsInMemFileDB.js:2017:29)
    at Object.checkObjectRights (/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/objects/objectsUtils.js:581:16)
    at ObjectsInMemoryServer.setObject (/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/objects/objectsInMemFileDB.js:2013:15)
    at RandomBytes.require.randomBytes [as ondone] (/tmp/test-iobroker.virtualpowermeter/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:113:37)
npm WARN notsup Unsupported engine for iobroker.js-controller@3.0.8: wanted: {"node":">=10.0.0"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: iobroker.js-controller@3.0.8
npm WARN notsup Unsupported engine for mkdirp@1.0.4: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: mkdirp@1.0.4
npm WARN notsup Unsupported engine for semver@7.3.0: wanted: {"node":">=10"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: semver@7.3.0
npm WARN notsup Unsupported engine for tar@6.0.1: wanted: {"node":">= 10"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: tar@6.0.1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN notsup Unsupported engine for rsa-compat@2.0.8: wanted: {"node":">=10.12"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: rsa-compat@2.0.8
npm WARN notsup Unsupported engine for rsa-compat@1.9.4: wanted: {"node":">=10.12"} (current: {"node":"8.17.0","npm":"6.13.4"})
npm WARN notsup Not compatible with your version of node/npm: rsa-compat@1.9.4
npm WARN test-iobroker.virtualpowermeter@1.0.0 No description
npm WARN test-iobroker.virtualpowermeter@1.0.0 No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.js-controller@3.0.8 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the iobroker.js-controller@3.0.8 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2020-04-14T10_52_52_010Z-debug.log
    1) "before all" hook

ich konnte den Adapter noch nicht auf js-controller 3.x testen da ich als testsystem aktuell nur Windows verwende.

wird nodejs 8 nicht mehr unterstütz? soll man einfach den Node 8 test rausnehmen oder die travis.yml komplett überarbeiten?

[omega235]

ich habe den Support für nodejs 8 rausgeschmissen

[simatec]

@omega235
Anstelle von node 8 jetzt einfach node in die travis.yml

os:
  - linux
  - osx
  - windows
language: node_js
node_js:
  - '10'
  - '12'
  - 'node'
before_script:
  - export NPMVERSION=$(echo "$($(which npm) -v)"|cut -c1)
  - 'if [[ $NPMVERSION == 5 ]]; then npm install -g npm@5; fi'
  - npm -v
env:
  - CXX=g++-6
addons:
  apt:
    sources:
      - ubuntu-toolchain-r-test
    packages:
      - g++-6
script:
  - 'npm run test:package'
  - 'npm run test:integration'