Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Gyp err! stack Error: `gyp` faild with exit code:1 (Windows)

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Gyp err! stack Error: `gyp` faild with exit code:1 (Windows)

    This topic has been deleted. Only users with topic management privileges can see it.
    • Patrick
      Patrick last edited by

      Ich habe immer wider bei der Installation von dem Adapter Amazon Button und Zwave diesen Fehler "gyp err! stack Error: gyp faild with exit code:1"

      das hier habe ich schon mehrfach versucht und auch andere Sachen die ich im Internet gefunden habe

      npm cache clean
      npm install node-gyp -g --force
      

      da nach kam kurz ein anderer Fehler, nach ein paar Neustarts kam er wider, der gleiche Fehler ( gyp err! stack Error: gyp faild with exit code:1 )

      hatte das Problem schon mal jemand

      alles wurde unter Admin gemacht

      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 last edited by

        Hast Du den Fehler ein bissl ausführlicher?

        Welche Node und NPM version? (node -v / npm -v)

        1 Reply Last reply Reply Quote 0
        • Patrick
          Patrick last edited by

          @apollon77:

          Hast Du den Fehler ein bissl ausführlicher?

          Welche Node und NPM version? (node -v / npm -v) `
          node-v 4.6.1

          npm -v 2.15.9

          @Patrick:

          @Bluefox:

          @Patrick:

          habe jetzt noch mal das alte Backup aufgespielt und alles wie beschrieben gemacht

          jetzt kommt ein anderes Fehler

          ! C:\Users\rickfl>cd "C:\Program Files\IO BROKER\ioBroker"
          ! C:\Program Files\IO BROKER\ioBroker>npm install https://github.com/ioBroker/ioBroker.zw … all/master --production --unsafe-perm --build-from-source
          ! /
          ! > iobroker.zwave@0.4.3 preinstall C:\Program Files\IO BROKER\ioBroker\node_modules\iobroker.zwave
          ! > node lib/preinstall.js
          !
          ! > openzwave-shared@1.2.0 preinstall C:\Program Files\IO BROKER\ioBroker\node_modules\iobroker.zwave\node_modules\openzwave-shared
          ! > node lib/install-ozw.js
          ! Installing Open Z-Wave
          ! Installing dependencies to C:\Users\rickfl\AppData\Local\Temp\ozwinstall-yeew830izfr
          ! npm WARN deprecated wrench@1.5.9: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.
          ! module.js:327
          ! throw err;
          ! ^
          ! Error: Cannot find module 'C:\Users\rickfl\AppData\Local\Temp\ozwinstall-yeew830izfr/node_modules/request'
          ! at Function.Module._resolveFilename (module.js:325:15)
          ! at Function.Module._load (module.js:276:25)
          ! at Module.require (module.js:353:17)
          ! at require (internal/module.js:12:17)
          ! at Module.module.exports (C:\Program Files\IO BROKER\ioBroker\node_modules\iobroker.zwave\node_modules\openzwave-shared\lib\install-ozw.js:165:13)
          ! at Object. <anonymous>(C:\Program Files\IO BROKER\ioBroker\node_modules\iobroker.zwave\node_modules\openzwave-shared\lib\install-ozw.js:220:12)
          ! at Module._compile (module.js:409:26)
          ! at Object.Module._extensions..js (module.js:416:10)
          ! at Module.load (module.js:343:32)
          ! at Function.Module._load (module.js:300:12)
          ! npm ERR! Windows_NT 10.0.10586
          ! npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "https://github.com/ioBroker/ioBroker.zw ... all/master" "--production" "--unsafe-perm" "--build-from-source"
          ! npm ERR! node v4.6.1
          ! npm ERR! npm v2.15.9
          ! npm ERR! code ELIFECYCLE
          ! npm ERR! openzwave-shared@1.2.0 preinstall: node lib/install-ozw.js
          ! npm ERR! Exit status 1
          ! npm ERR!
          ! npm ERR! Failed at the openzwave-shared@1.2.0 preinstall script 'node lib/install-ozw.js'.
          ! npm ERR! This is most likely a problem with the openzwave-shared package,
          ! npm ERR! not with npm itself.
          ! npm ERR! Tell the author that this fails on your system:
          ! npm ERR! node lib/install-ozw.js
          ! npm ERR! You can get information on how to open an issue for this project with:
          ! npm ERR! npm bugs openzwave-shared
          ! npm ERR! Or if that isn't available, you can get their info via:
          ! npm ERR!
          ! npm ERR! npm owner ls openzwave-shared
          ! npm ERR! There is likely additional logging output above.
          ! npm ERR! Please include the following file with any support request:
          ! npm ERR! C:\Program Files\IO BROKER\ioBroker\npm-debug.log
          ! C:\Program Files\IO BROKER\ioBroker></anonymous> `
          Also es gibt tatsächlich das Problem mit Windows.

          Die Leute arbeiten dran, aber es gibt immer noch keine Lösung:

          https://github.com/felixrieseberg/windo … s/issues/9

          Workaround: Install Visual C++ projects support to Visual Studio 2015 (requires 3GB space).(C++ option aktivieren) `

          dann warte ich mal ab `
          1083_unbenannt.png

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Support us

          ioBroker
          Community Adapters
          Donate

          536
          Online

          31.8k
          Users

          80.0k
          Topics

          1.3m
          Posts

          2
          3
          1085
          Loading More Posts
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes
          Reply
          • Reply as topic
          Log in to reply
          Community
          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
          The ioBroker Community 2014-2023
          logo