Can 't install node-red-contrib-audio 1.0.2

Hi, i want to install on a fresh raspbian buster installation with node red the following audio node:

i got following error log:

Please advise:

2019-10-09T10:55:30.909Z installieren : node-red-contrib-audio 1.0.2

2019-10-09T10:55:31.110Z npm install --no-audit --no-update-notifier --save --save-prefix="~" --production node-red-contrib-audio@1.0.2
2019-10-09T10:55:35.635Z [err] npm
2019-10-09T10:55:35.636Z [err]
2019-10-09T10:55:35.637Z [err] WARN npm npm does not support Node.js v10.15.2
2019-10-09T10:55:35.638Z [err] npm
2019-10-09T10:55:35.639Z [err] WARN npm You should probably upgrade to a newer version of node as we
2019-10-09T10:55:35.639Z [err] npm
2019-10-09T10:55:35.639Z [err] WARN npm can't make any promises that npm will work with this version.
2019-10-09T10:55:35.640Z [err] npm
2019-10-09T10:55:35.640Z [err] WARN npm
2019-10-09T10:55:35.641Z [err] Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
2019-10-09T10:55:35.641Z [err] npm WARN npm You can find the latest version at
2019-10-09T10:55:42.937Z [out]
2019-10-09T10:55:42.937Z [out] > speaker@0.3.1 install /home/pi/.node-red/node_modules/speaker
2019-10-09T10:55:42.937Z [out] > node-gyp rebuild
2019-10-09T10:55:42.937Z [out]
2019-10-09T10:55:50.982Z [out] make: Verzeichnis „/home/pi/.node-red/node_modules/speaker/build“ wird betreten
2019-10-09T10:55:50.988Z [out] CC(target) Release/
2019-10-09T10:55:51.483Z [err] ../deps/mpg123/src/output/alsa.c:19:10: fatal error: alsa/asoundlib.h: Datei oder Verzeichnis nicht gefunden
2019-10-09T10:55:51.483Z [err] #include <alsa/asoundlib.h>
2019-10-09T10:55:51.483Z [err] ^~~~~~~~~~~~~~~~~~
2019-10-09T10:55:51.483Z [err] compilation terminated.
2019-10-09T10:55:51.485Z [err] make: *** [deps/mpg123/ Release/] Fehler 1
2019-10-09T10:55:51.485Z [out] make: Verzeichnis „/home/pi/.node-red/node_modules/speaker/build“ wird verlassen
2019-10-09T10:55:51.491Z [err] gyp
2019-10-09T10:55:51.493Z [err]
2019-10-09T10:55:51.493Z [err] ERR! build error
2019-10-09T10:55:51.496Z [err] gyp
2019-10-09T10:55:51.496Z [err] ERR! stack Error: make failed with exit code: 2
2019-10-09T10:55:51.496Z [err] gyp
2019-10-09T10:55:51.496Z [err] ERR! stack at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:262:23)
2019-10-09T10:55:51.496Z [err] gyp ERR!
2019-10-09T10:55:51.497Z [err] stack at ChildProcess.emit (events.js:189:13)
2019-10-09T10:55:51.497Z [err] gyp
2019-10-09T10:55:51.497Z [err] ERR!
2019-10-09T10:55:51.497Z [err] stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
2019-10-09T10:55:51.498Z [err] gyp
2019-10-09T10:55:51.499Z [err] ERR! System Linux 4.19.75-v7+
2019-10-09T10:55:51.499Z [err] gyp
2019-10-09T10:55:51.500Z [err] ERR! command
2019-10-09T10:55:51.500Z [err] "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
2019-10-09T10:55:51.500Z [err] gyp
2019-10-09T10:55:51.500Z [err] ERR! cwd
2019-10-09T10:55:51.500Z [err] /home/pi/.node-red/node_modules/speaker
2019-10-09T10:55:51.500Z [err] gyp
2019-10-09T10:55:51.501Z [err] ERR! node -v v10.15.2
2019-10-09T10:55:51.501Z [err] gyp
2019-10-09T10:55:51.501Z [err] ERR! node-gyp -v v3.8.0
2019-10-09T10:55:51.501Z [err] gyp
2019-10-09T10:55:51.501Z [err] ERR!
2019-10-09T10:55:51.502Z [err] not ok
2019-10-09T10:55:52.103Z [err] npm
2019-10-09T10:55:52.104Z [err] ERR! code ELIFECYCLE
2019-10-09T10:55:52.104Z [err] npm
2019-10-09T10:55:52.105Z [err] ERR! errno 1
2019-10-09T10:55:52.110Z [err] npm
2019-10-09T10:55:52.111Z [err] ERR! speaker@0.3.1 install: node-gyp rebuild
2019-10-09T10:55:52.111Z [err] npm ERR!
2019-10-09T10:55:52.111Z [err] Exit status 1
2019-10-09T10:55:52.111Z [err] npm ERR!
2019-10-09T10:55:52.111Z [err]
2019-10-09T10:55:52.111Z [err] npm ERR!
2019-10-09T10:55:52.112Z [err] Failed at the speaker@0.3.1 install script.
2019-10-09T10:55:52.112Z [err] npm
2019-10-09T10:55:52.112Z [err] ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-10-09T10:55:52.155Z [err]
2019-10-09T10:55:52.155Z [err] npm
2019-10-09T10:55:52.158Z [err] ERR! A complete log of this run can be found in:
2019-10-09T10:55:52.158Z [err] npm ERR! /home/pi/.npm/_logs/2019-10-09T10_55_52_125Z-debug.log
2019-10-09T10:55:52.180Z rc=1

Did you read the node's README and see if there were an Prerequirements?

see here -