Siot / PaWebControl

PulseAudio Web Volume Control
GNU General Public License v3.0
46 stars 16 forks source link

Can't get it to build #31

Closed YtvwlD closed 5 years ago

YtvwlD commented 5 years ago

I've tried to install the new version (with the rewritten backend), but failed (after I installed grunt and Java).

This is the log:

$ npm run build
> pawebcontrol@2.0.0 prebuild /code
> rimraf dist && mkdir dist && cd node_modules/jquery-ui/ && grunt jenkins

Running "asciilint" task
>> 21 files lint free.

Running "jshint:all" (jshint) task
>> 158 files lint free.

Running "jscs:ui" (jscs) task
>> 135 files without code style errors.

Running "jscs:tests" (jscs) task
>> 133 files without code style errors.

Running "csslint:base_theme" (csslint) task
>> 22 files lint free.

Running "htmllint:good" (htmllint) task
>> 245 files lint free.

Running "htmllint:bad" (htmllint) task
>> 6 files lint free.

Running "requirejs:js" (requirejs) task

Running "qunit:files" (qunit) task
Testing tests/unit/accordion/accordion.html Fatal error: spawn /code/node_modules/jquery-ui/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs ENOENT
npm ERR! code ELIFECYCLE
npm ERR! errno 3
npm ERR! pawebcontrol@2.0.0 prebuild: `rimraf dist && mkdir dist && cd node_modules/jquery-ui/ && grunt jenkins`
npm ERR! Exit status 3
npm ERR! 
npm ERR! Failed at the pawebcontrol@2.0.0 prebuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Siot commented 5 years ago

Hi @YtvwlD, have you done a first time "npm install" without errors? what's your operating system?

YtvwlD commented 5 years ago

This was the output of npm install:


> phantomjs-prebuilt@2.1.16 install /code/node_modules/jquery-ui/node_modules/phantomjs-prebuilt
> node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
Saving to /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
Receiving...

Received 22866K total.
Extracting tar contents (via spawned process)
Removing /code/node_modules/jquery-ui/node_modules/phantomjs-prebuilt/lib/phantom
Copying extracted folder /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2-extract-1563211983760/phantomjs-2.1.1-linux-x86_64 -> /code/node_modules/jquery-ui/node_modules/phantomjs-prebuilt/lib/phantom
Writing location.js file
Done. Phantomjs binary available at /code/node_modules/jquery-ui/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs

> husky@2.0.0 install /code/node_modules/husky
> node husky install

husky > setting up git hooks
husky > done

> commitplease@2.3.0 install /code/node_modules/jquery-ui/node_modules/commitplease
> node install

Could not find git repo in /code/node_modules/jquery-ui/.git
npm WARN lifecycle pawebcontrol@2.0.0~postinstall: cannot run in wd pawebcontrol@2.0.0 cd node_modules/jquery-ui && npm install (wd=/code)                                                                    
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):                
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})                                             

added 1562 packages from 684 contributors and audited 20982 packages in 81.413s
found 417 vulnerabilities (63 low, 7 moderate, 347 high)
  run `npm audit fix` to fix them, or `npm audit` for details

Edit: This is all inside a Docker container running Alpine.

Siot commented 5 years ago

I've updated some old dependencies. please try again.

YtvwlD commented 5 years ago

I did. And it built successfully. (I didn't yet test whether the application really works, but it builds now.)

Siot commented 5 years ago

I've wrote some lines about Dockerization: https://github.com/Siot/PaWebControl/wiki/Thoughts-on-dockerization

YtvwlD commented 5 years ago

Thank you.

Your thoughts about Dockerization are not entirely correct. It is possible to connect to a pulse server running outside the container by setting the environment variable PULSE_SERVER. (Here is the Dockerfile I'm currently using.)