==> Beginne build()...
npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated

> core-js@2.6.12 postinstall /data/local/hgr/src/homegear-ui/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/@babel/cli/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN shif@1.0.0 No repository field.
npm WARN shif@1.0.0 license should be a valid SPDX license expression

added 814 packages from 305 contributors and audited 816 packages in 22.158s

25 packages are looking for funding
  run `npm fund` for details

found 1 low severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details

> shif@1.0.0 build /data/local/hgr/src/homegear-ui
> php admin/admin.php generateExtensions && npm run babel

homegear
default
menu
user
shading
window
door
generic
icons
info
lighting
socket
status
climate
heating
ventilation
timer
media
components
house

homegearws: homegearws.min.js | 
jquery: jquery.min.js | 
vue: vue.js | 
vue-router: vue-router.js | 
sortablejs: sortable.min.js | sortable.umd.js | 
vuedraggable: vuedraggable.umd.min.js | 
flaticons: Warning: Nicht vorhanden -> /data/local/hgr/src/homegear-ui/admin/assets/masters/flaticons
iro: iro.min.js | 
webauthn: Warning: Nicht vorhanden -> /data/local/hgr/src/homegear-ui/admin/assets/masters/webauthn

/admin/favicon.ico
/admin/favicon.png
/interfacedata.custom.php.tmpl
/interfacedata.php
/admin/manifest.json
/admin/manifest.webapp
/setup.php
/admin/signin.php
/admin/user.php
/admin/webauthnServer.php
/admin/assets/fonts
/admin/media/images
/admin/media/logo
/admin/assets/WebAuthn

> shif@1.0.0 babel /data/local/hgr/src/homegear-ui
> npx babel dist/script.js --out-file dist/script.min.js

Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. (While processing preset: "/data/local/hgr/src/homegear-ui/node_modules/@babel/preset-env/lib/index.js")
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! shif@1.0.0 babel: `npx babel dist/script.js --out-file dist/script.min.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the shif@1.0.0 babel 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/henning/.npm/_logs/2021-01-26T17_25_22_411Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! shif@1.0.0 build: `php admin/admin.php generateExtensions && npm run babel`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the shif@1.0.0 build 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/henning/.npm/_logs/2021-01-26T17_25_22_454Z-debug.log