Is it possible to install tf playground on IBM Power architecture??

[michalkordyzon]

After entering the command 'npm install' in the directory with playground files I got following message:

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: [email protected]

Here is my environment:

uname -a

Linux minsky2 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:26:02 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

lscpu

Architecture:          ppc64le
Byte Order:            Little Endian
CPU(s):                160
On-line CPU(s) list:   0-159
Thread(s) per core:    8
Core(s) per socket:    10
Socket(s):             2
NUMA node(s):          2
Model:                 1.0 (pvr 004c 0100)
Model name:            POWER8NVL (raw), altivec supported
CPU max MHz:           4023.0000
CPU min MHz:           2061.0000
Hypervisor vendor:     horizontal
Virtualization type:   full
L1d cache:             64K
L1i cache:             32K
L2 cache:              512K
L3 cache:              8192K
NUMA node0 CPU(s):     0-79
NUMA node1 CPU(s):     80-159

cat /usr/local/playground/npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'build' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle [email protected]~prebuild: [email protected]
6 silly lifecycle [email protected]~prebuild: no script for prebuild, continuing
7 info lifecycle [email protected]~build: [email protected]
8 verbose lifecycle [email protected]~build: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~build: PATH: /usr/share/npm/bin/node-gyp-bin:/usr/local/playground/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
10 verbose lifecycle [email protected]~build: CWD: /usr/local/playground
11 silly lifecycle [email protected]~build: Args: [ '-c',
11 silly lifecycle   'npm run prep && npm run build-js && npm run build-css && npm run build-html' ]
12 silly lifecycle [email protected]~build: Returned: code: 1  signal: null
13 info lifecycle [email protected]~build: Failed to exec build script
14 verbose stack Error: [email protected] build: `npm run prep && npm run build-js && npm run build-css && npm run build-html`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at EventEmitter.emit (events.js:172:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at ChildProcess.emit (events.js:172:7)
14 verbose stack     at maybeClose (internal/child_process.js:821:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid [email protected]
16 verbose cwd /usr/local/playground
17 error Linux 4.4.0-97-generic
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
19 error node v4.2.6
20 error npm  v3.5.2
21 error code ELIFECYCLE
22 error [email protected] build: `npm run prep && npm run build-js && npm run build-css && npm run build-html`
22 error Exit status 1
23 error Failed at the [email protected] build script 'npm run prep && npm run build-js && npm run build-css && npm run build-html'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the deep-playground-prototype package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     npm run prep && npm run build-js && npm run build-css && npm run build-html
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs deep-playground-prototype
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls deep-playground-prototype
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]