[GH-ISSUE #1077] Installation fails on ARM because Cypress is not available for the platform

kerem commented

2026-02-26 02:33:45 +03:00

Owner

Originally created by @glics on GitHub (Sep 11, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/1077

When trying to install Koel on my Raspberry Pi the installation failed because Cypress could not find a supported version to download.
I don't think Cypress even has an ARM compatible version, and here it is trying to download the IA32 version? Wtf
Besides, is a test library supposed to be a requirement for the installation?
Here's the error log for php artisan koel:init, after the yarn install command:

├── Installing Node modules in resources/assets directory
yarn install v1.17.3
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.9: The platform "linux" is incompatible with this module.
info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@2.0.7: The platform "linux" is incompatible with this module.
info "fsevents@2.0.7" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /home/glics/koel/node_modules/cypress: Command failed.
Exit code: 1
Command: node index.js --exec install
Arguments:
Directory: /home/glics/koel/node_modules/cypress
Output:
Installing Cypress (version: 3.4.1)

[19:28:41]  Downloading Cypress     [started]
[19:29:08]  Downloading Cypress     [failed]
[19:29:08] → The Cypress App could not be downloaded.

Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration

Otherwise, please check network connectivity and try again:

----------

URL: https://download.cypress.io/desktop/3.4.1?platform=linux&arch=ia32
Error: Failed downloading the Cypress binary.
Response code: 404
Response message: Not Found

----------

Platform: linux (Debian - 10)
Cypress Version: 3.4.1
The Cypress App could not be downloaded.

Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration

Otherwise, please check network connectivity and try again:

----------

URL: https://download.cypress.io/desktop/3.4.1?platform=linux&arch=ia32
Error: Failed downloading the Cypress binary.
Response code: 404
Response message: Not Found

----------

Platform: linux (Debian - 10)
Cypress Version: 3.4.1

info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Here are the steps to reproduce.

Platform: ARMv7 (Raspberry Pi 2) or ARMv8 (Raspberry Pi 3 and later), though I guess any ARM version goes (i.e. mobile devices with Termux)
OS: Raspbian (Debian) 10 Buster
PHP version: 7.3.9 with the required moudules such as php-xml, php-curl, php-pgsql, php-mbstring
Any DBMS goes, I used PostgreSQL
Yarn version 1.17.3
Laravel Framework 5.8.35
Composer version 1.9.0

Clone the repository git clone https://github.com/phanan/koel
Checkout the 4.0.0 release git checkout v4.0.0
(unnecessary?) Give permissions for the directory chmod -R 777 .
Install composer modules composer install
Start installation with php artisan koel:init, fill in the env variables as needed and wait for yarn install's stage 4, Building fresh packages. At this point within some seconds Cypress will fail to find a version for ARM.

Really hoping this can be sorted out, love to see NodeJS and PHP being used for personal music streaming instead of the many Subsonic java-based forks

Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:

You have read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting
The issue has not been reported before
This is not a "how to install on Windows" or "why is my npm messed up" question
You're a cool person

All checked? Now also make sure your issue

Is associated with a version. Or better yet, a commit.
Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?)
Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know)
Is in English, 因为我不说中文。

Originally created by @glics on GitHub (Sep 11, 2019). Original GitHub issue: https://github.com/koel/koel/issues/1077 When trying to install Koel on my Raspberry Pi the installation failed because Cypress could not find a supported version to download. I don't think Cypress even has an ARM compatible version, and here it is trying to download the IA32 version? Wtf Besides, is a test library supposed to be a requirement for the installation? Here's the error log for `php artisan koel:init`, after the yarn install command: ``` ├── Installing Node modules in resources/assets directory yarn install v1.17.3 [1/4] Resolving packages... [2/4] Fetching packages... info fsevents@1.2.9: The platform "linux" is incompatible with this module. info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation. info fsevents@2.0.7: The platform "linux" is incompatible with this module. info "fsevents@2.0.7" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh packages... error /home/glics/koel/node_modules/cypress: Command failed. Exit code: 1 Command: node index.js --exec install Arguments: Directory: /home/glics/koel/node_modules/cypress Output: Installing Cypress (version: 3.4.1) [19:28:41] Downloading Cypress [started] [19:29:08] Downloading Cypress [failed] [19:29:08] → The Cypress App could not be downloaded. Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration Otherwise, please check network connectivity and try again: ---------- URL: https://download.cypress.io/desktop/3.4.1?platform=linux&arch=ia32 Error: Failed downloading the Cypress binary. Response code: 404 Response message: Not Found ---------- Platform: linux (Debian - 10) Cypress Version: 3.4.1 The Cypress App could not be downloaded. Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration Otherwise, please check network connectivity and try again: ---------- URL: https://download.cypress.io/desktop/3.4.1?platform=linux&arch=ia32 Error: Failed downloading the Cypress binary. Response code: 404 Response message: Not Found ---------- Platform: linux (Debian - 10) Cypress Version: 3.4.1 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ``` Here are the steps to reproduce. - Platform: ARMv7 (Raspberry Pi 2) or ARMv8 (Raspberry Pi 3 and later), though I guess any ARM version goes (i.e. mobile devices with Termux) - OS: Raspbian (Debian) 10 Buster - PHP version: 7.3.9 with the required moudules such as php-xml, php-curl, php-pgsql, php-mbstring - Any DBMS goes, I used PostgreSQL - Yarn version 1.17.3 - Laravel Framework 5.8.35 - Composer version 1.9.0 1. Clone the repository `git clone https://github.com/phanan/koel` 2. Checkout the 4.0.0 release `git checkout v4.0.0` 3. (unnecessary?) Give permissions for the directory `chmod -R 777 .` 4. Install composer modules `composer install` 5. Start installation with `php artisan koel:init`, fill in the env variables as needed and wait for `yarn install`'s stage 4, `Building fresh packages`. At this point within some seconds Cypress will fail to find a version for ARM. Really hoping this can be sorted out, love to see NodeJS and PHP being used for personal music streaming instead of the many Subsonic java-based forks ----- Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue: - [x] You have read and followed closely the [Wiki](https://koel.phanan.net/docs), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://koel.phanan.net/docs/#/troubleshooting) - [x] The issue has not been reported before - [x] This is not a "how to install on Windows" or "why is my npm messed up" question - [ ] You're a cool person All checked? Now also make sure your issue - [x] Is associated with a version. Or better yet, a commit. - [x] Is as detailed as possible (ahem... OS, browser, steps to reproduce, maybe?) - [x] Includes the error output if it's a bug/error report ("Whoops!" is not very helpful, you know) - [x] Is in English, 因为我不说中文。

kerem

2026-02-26 02:33:45 +03:00

closed this issue
added the
[Type] Help Request
label

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@SpikeShape commented on GitHub (Sep 12, 2019):

Same for me running Raspbian 9 on a Raspberry Pi 3.

After the 404 the installation process seems to be stuck showing these message:

----------

Platform: linux (Debian - 9.6)
Cypress Version: 3.4.1

info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

@SpikeShape commented on GitHub (Sep 12, 2019): Same for me running Raspbian 9 on a Raspberry Pi 3. After the 404 the installation process seems to be stuck showing these message: ``` ---------- Platform: linux (Debian - 9.6) Cypress Version: 3.4.1 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ```

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 12, 2019):

What happens if you remove the cypress dependency from package.json?

@phanan commented on GitHub (Sep 12, 2019): What happens if you remove the cypress dependency from package.json?

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@glics commented on GitHub (Sep 12, 2019):

I started with a clean git clone and ran yarn remove cypress.
After compiling all the dependencies (Spoiler alert - node-sass takes some time) it finished without errors.
I ran:
composer install
php artisan koel:init
Filled in the fields again and the build succeeded, then failed again but I guess this was my error.

Here's the relevant output

Now to front-end stuff
├── Installing Node modules in resources/assets directory
yarn install v1.17.3
[1/4] Resolving packages...
success Already up-to-date.
Done in 8.56s.
└── Compiling assets
yarn install v1.17.3
[1/4] Resolving packages...
success Already up-to-date.
Done in 8.50s.
yarn run v1.17.3
$ cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js --colors
 95% emitting ERROR  Failed to compile with 4 errors10:51:25 AM

These dependencies were not found:

* /home/glics/koel/resources/assets/js/app.js in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss
* /home/glics/koel/resources/assets/js/remote/app.js in multi ./resources/assets/js/remote/app.js
* /home/glics/koel/resources/assets/sass/app.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss
* /home/glics/koel/resources/assets/sass/remote.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss

To install them, you can run: npm install --save /home/glics/koel/resources/assets/js/app.js /home/glics/koel/resources/assets/js/remote/app.js /home/glics/koel/resources/assets/sass/app.scss /home/glics/koel/resources/assets/sass/remote.scss
fs.js:115
    throw err;
    ^

Error: ENOENT: no such file or directory, stat '/home/glics/koel/resources/assets/img'
    at Object.statSync (fs.js:851:3)
    at Object.statSync (/home/glics/koel/node_modules/graceful-fs/polyfills.js:308:16)
    at Object.copySync (/home/glics/koel/node_modules/fs-extra/lib/copy-sync/copy-sync.js:31:86)
    at File.copyTo (/home/glics/koel/node_modules/laravel-mix/src/File.js:210:12)
    at FileCollection.copyTo (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:88:24)
    at src.forEach.file (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:82:38)
    at Array.forEach (<anonymous>)
    at FileCollection.copyTo (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:82:17)
    at CopyFilesTask.run (/home/glics/koel/node_modules/laravel-mix/src/tasks/CopyFilesTask.js:14:20)
    at CustomTasksPlugin.runTask (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:34:14)
    at Mix.tasks.forEach.task (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:44)
    at Array.forEach (<anonymous>)
    at Compiler.compiler.plugin.stats (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:23)
    at Compiler.applyPlugins (/home/glics/koel/node_modules/tapable/lib/Tapable.js:61:14)
    at emitRecords.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:264:11)
    at Compiler.emitRecords (/home/glics/koel/node_modules/webpack/lib/Compiler.js:371:38)
    at emitAssets.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:258:10)
    at applyPluginsAsyncSeries1.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:364:12)
    at next (/home/glics/koel/node_modules/tapable/lib/Tapable.js:218:11)
    at Compiler.compiler.plugin (/home/glics/koel/node_modules/webpack/lib/performance/SizeLimitsPlugin.js:99:4)
    at Compiler.applyPluginsAsyncSeries1 (/home/glics/koel/node_modules/tapable/lib/Tapable.js:222:13)
    at Compiler.afterEmit (/home/glics/koel/node_modules/webpack/lib/Compiler.js:361:9)
    at require.forEach.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:350:15)
    at /home/glics/koel/node_modules/async/dist/async.js:473:16
    at iteratorCallback (/home/glics/koel/node_modules/async/dist/async.js:1064:13)
    at /home/glics/koel/node_modules/async/dist/async.js:969:16
    at /home/glics/koel/node_modules/graceful-fs/graceful-fs.js:57:14
    at FSReqWrap.oncomplete (fs.js:141:20)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Oops! Koel installation or upgrade didn't finish successfully.
Please try again, or visit https://koel.phanan.net/docs for manual installation.
�😥 Sorry for this. You deserve bette

(Yes it said bette. No I don't, I love you anyway my dear)

Looking inside resources/assets/ it's just empty. I think I should have used git clone --recursive?

EDIT - totally should, and I should also have read the updated documentation. Cloning the submodules now, will update soon

@glics commented on GitHub (Sep 12, 2019): I started with a clean git clone and ran `yarn remove cypress`. After compiling all the dependencies (Spoiler alert - node-sass takes some time) it finished without errors. I ran: `composer install` `php artisan koel:init` Filled in the fields again and the build succeeded, then failed again but I guess this was my error. Here's the relevant output ``` Now to front-end stuff ├── Installing Node modules in resources/assets directory yarn install v1.17.3 [1/4] Resolving packages... success Already up-to-date. Done in 8.56s. └── Compiling assets yarn install v1.17.3 [1/4] Resolving packages... success Already up-to-date. Done in 8.50s. yarn run v1.17.3 $ cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js --colors 95% emitting ERROR Failed to compile with 4 errors10:51:25 AM These dependencies were not found: * /home/glics/koel/resources/assets/js/app.js in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss * /home/glics/koel/resources/assets/js/remote/app.js in multi ./resources/assets/js/remote/app.js * /home/glics/koel/resources/assets/sass/app.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss * /home/glics/koel/resources/assets/sass/remote.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss To install them, you can run: npm install --save /home/glics/koel/resources/assets/js/app.js /home/glics/koel/resources/assets/js/remote/app.js /home/glics/koel/resources/assets/sass/app.scss /home/glics/koel/resources/assets/sass/remote.scss fs.js:115 throw err; ^ Error: ENOENT: no such file or directory, stat '/home/glics/koel/resources/assets/img' at Object.statSync (fs.js:851:3) at Object.statSync (/home/glics/koel/node_modules/graceful-fs/polyfills.js:308:16) at Object.copySync (/home/glics/koel/node_modules/fs-extra/lib/copy-sync/copy-sync.js:31:86) at File.copyTo (/home/glics/koel/node_modules/laravel-mix/src/File.js:210:12) at FileCollection.copyTo (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:88:24) at src.forEach.file (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:82:38) at Array.forEach (<anonymous>) at FileCollection.copyTo (/home/glics/koel/node_modules/laravel-mix/src/FileCollection.js:82:17) at CopyFilesTask.run (/home/glics/koel/node_modules/laravel-mix/src/tasks/CopyFilesTask.js:14:20) at CustomTasksPlugin.runTask (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:34:14) at Mix.tasks.forEach.task (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:44) at Array.forEach (<anonymous>) at Compiler.compiler.plugin.stats (/home/glics/koel/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:9:23) at Compiler.applyPlugins (/home/glics/koel/node_modules/tapable/lib/Tapable.js:61:14) at emitRecords.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:264:11) at Compiler.emitRecords (/home/glics/koel/node_modules/webpack/lib/Compiler.js:371:38) at emitAssets.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:258:10) at applyPluginsAsyncSeries1.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:364:12) at next (/home/glics/koel/node_modules/tapable/lib/Tapable.js:218:11) at Compiler.compiler.plugin (/home/glics/koel/node_modules/webpack/lib/performance/SizeLimitsPlugin.js:99:4) at Compiler.applyPluginsAsyncSeries1 (/home/glics/koel/node_modules/tapable/lib/Tapable.js:222:13) at Compiler.afterEmit (/home/glics/koel/node_modules/webpack/lib/Compiler.js:361:9) at require.forEach.err (/home/glics/koel/node_modules/webpack/lib/Compiler.js:350:15) at /home/glics/koel/node_modules/async/dist/async.js:473:16 at iteratorCallback (/home/glics/koel/node_modules/async/dist/async.js:1064:13) at /home/glics/koel/node_modules/async/dist/async.js:969:16 at /home/glics/koel/node_modules/graceful-fs/graceful-fs.js:57:14 at FSReqWrap.oncomplete (fs.js:141:20) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. Oops! Koel installation or upgrade didn't finish successfully. Please try again, or visit https://koel.phanan.net/docs for manual installation. �😥 Sorry for this. You deserve bette ``` (Yes it said bette. No I don't, I love you anyway my dear) Looking inside resources/assets/ it's just empty. I think I should have used `git clone --recursive`? EDIT - totally should, and I should also have read the updated documentation. Cloning the submodules now, will update soon

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 12, 2019):

Hmm, maybe it's worth to add a check for resources/assets content and throw an early, more meaningful error 🤔.

@phanan commented on GitHub (Sep 12, 2019): Hmm, maybe it's worth to add a check for `resources/assets` content and throw an early, more meaningful error 🤔.

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 12, 2019):

How can it say "bette" btw 😆. This is the relevant code:

        } catch (Exception $e) {
            $this->error("Oops! Koel installation or upgrade didn't finish successfully.");
            $this->error('Please try again, or visit '.config('koel.misc.docs_url').' for manual installation.');
            $this->error('😥 Sorry for this. You deserve better.');

            return;
        }

@phanan commented on GitHub (Sep 12, 2019): How can it say "bette" btw 😆. This is the relevant code: ```php } catch (Exception $e) { $this->error("Oops! Koel installation or upgrade didn't finish successfully."); $this->error('Please try again, or visit '.config('koel.misc.docs_url').' for manual installation.'); $this->error('😥 Sorry for this. You deserve better.'); return; } ```

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@glics commented on GitHub (Sep 12, 2019):

Still not sure about that lol.

Now I have another error during Vue's build:

 error  in ./resources/assets/img/bars.gif

Module build failed: Error: spawn /home/glics/koel/node_modules/gifsicle/vendor/gifsicle ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)

 @ ./node_modules/vue-loader/lib/template-compiler?{"id":"data-v-18d0a972","hasScoped":true,"buble":{"transforms":{"stripWithFunctional":true}}}!./node_modules/vue-loader/lib/selector.js?type=template&index=0!./resources/assets/js/components/ui/sound-bar.vue 2:117-145
 @ ./resources/assets/js/components/ui/sound-bar.vue
 @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/ui/overlay.vue
 @ ./resources/assets/js/components/ui/overlay.vue
 @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/app.vue 
 @ ./resources/assets/js/app.vue
 @ ./resources/assets/js/app.js
 @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss

checking into node_modules/gifsicle/ the vendor folder is not there, looks like a yarn failure this time and at this point it's unrelated to ARM, I should be able to fix this with a yarn add gifsicle@3.0.4 m right?

@glics commented on GitHub (Sep 12, 2019): Still not sure about that lol. Now I have another error during Vue's build: ``` error in ./resources/assets/img/bars.gif Module build failed: Error: spawn /home/glics/koel/node_modules/gifsicle/vendor/gifsicle ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./node_modules/vue-loader/lib/template-compiler?{"id":"data-v-18d0a972","hasScoped":true,"buble":{"transforms":{"stripWithFunctional":true}}}!./node_modules/vue-loader/lib/selector.js?type=template&index=0!./resources/assets/js/components/ui/sound-bar.vue 2:117-145 @ ./resources/assets/js/components/ui/sound-bar.vue @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/ui/overlay.vue @ ./resources/assets/js/components/ui/overlay.vue @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/app.vue @ ./resources/assets/js/app.vue @ ./resources/assets/js/app.js @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss ``` checking into node_modules/gifsicle/ the vendor folder is not there, looks like a yarn failure this time and at this point it's unrelated to ARM, I should be able to fix this with a `yarn add gifsicle@3.0.4` m right?

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 12, 2019):

TBH I don’t know. ARM is unfamiliar water to me.

Giuseppe Careri notifications@github.com schrieb am Do. 12. Sep. 2019 um
13:02:

Still not sure about that lol.

Now I have another error during Vue's build:

error in ./resources/assets/img/bars.gif

Module build failed: Error: spawn /home/glics/koel/node_modules/gifsicle/vendor/gifsicle ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)

@ ./node_modules/vue-loader/lib/template-compiler?{"id":"data-v-18d0a972","hasScoped":true,"buble":{"transforms":{"stripWithFunctional":true}}}!./node_modules/vue-loader/lib/selector.js?type=template&index=0!./resources/assets/js/components/ui/sound-bar.vue 2:117-145
@ ./resources/assets/js/components/ui/sound-bar.vue
@ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":"env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}},"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/ui/overlay.vue
@ ./resources/assets/js/components/ui/overlay.vue
@ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":"env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}},"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/app.vue
@ ./resources/assets/js/app.vue
@ ./resources/assets/js/app.js
@ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss

checking into node_modules/gifsicle/ the vendor folder is not there, looks
like a yarn failure this time and at this point it's unrelated to ARM, I
should be able to fix this with a yarn add gifsicle@3.0.4 m right?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/1077?email_source=notifications&email_token=AB5O3UQ2XM3SYFO33UY52SLQJIOVNA5CNFSM4IVX5JN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6RP3NQ#issuecomment-530775478,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB5O3UVRH2MOX77ONJFESX3QJIOVNANCNFSM4IVX5JNQ
.

@phanan commented on GitHub (Sep 12, 2019): TBH I don’t know. ARM is unfamiliar water to me. Giuseppe Careri <notifications@github.com> schrieb am Do. 12. Sep. 2019 um 13:02: > Still not sure about that lol. > > Now I have another error during Vue's build: > > error in ./resources/assets/img/bars.gif > > Module build failed: Error: spawn /home/glics/koel/node_modules/gifsicle/vendor/gifsicle ENOENT > at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) > at onErrorNT (internal/child_process.js:415:16) > at process._tickCallback (internal/process/next_tick.js:63:19) > > @ ./node_modules/vue-loader/lib/template-compiler?{"id":"data-v-18d0a972","hasScoped":true,"buble":{"transforms":{"stripWithFunctional":true}}}!./node_modules/vue-loader/lib/selector.js?type=template&index=0!./resources/assets/js/components/ui/sound-bar.vue 2:117-145 > @ ./resources/assets/js/components/ui/sound-bar.vue > @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/ui/overlay.vue > @ ./resources/assets/js/components/ui/overlay.vue > @ ./resources/assets/node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":[["env",{"modules":false,"targets":{"browsers":["> 2%"],"uglify":true}}]],"plugins":["transform-object-rest-spread",["transform-runtime",{"polyfill":false,"helpers":false}]]}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/app.vue > @ ./resources/assets/js/app.vue > @ ./resources/assets/js/app.js > @ multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss > > checking into node_modules/gifsicle/ the vendor folder is not there, looks > like a yarn failure this time and at this point it's unrelated to ARM, I > should be able to fix this with a yarn add gifsicle@3.0.4 m right? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/1077?email_source=notifications&email_token=AB5O3UQ2XM3SYFO33UY52SLQJIOVNA5CNFSM4IVX5JN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6RP3NQ#issuecomment-530775478>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AB5O3UVRH2MOX77ONJFESX3QJIOVNANCNFSM4IVX5JNQ> > . >

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@SpikeShape commented on GitHub (Sep 12, 2019):

Same error here after removing cypress from the package file. But I can assure you that it says 'better' 😄

What I was thinking: Does the usual end user need cypress as a package at all? Wouldn't that be a dev dependency?

Edit:
I just checked: After the install process Koel seems to be up to date anyways: It just didn't show the loading bars gif but I have smart playlists, I see the new visualuzation and all that. The only thing that seems to be missing are gifs...

Edit 2:
What seems to be missing is the YouTube tab.

@SpikeShape commented on GitHub (Sep 12, 2019): Same error here after removing cypress from the package file. But I can assure you that it says 'better' 😄 What I was thinking: Does the usual end user need cypress as a package at all? Wouldn't that be a dev dependency? Edit: I just checked: After the install process Koel seems to be up to date anyways: It just didn't show the loading bars gif but I have smart playlists, I see the new visualuzation and all that. The only thing that seems to be missing are gifs... Edit 2: What seems to be missing is the YouTube tab.

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 12, 2019):

Cypress is a dev dependency (you can check the package.json file).

Spike Shape notifications@github.com schrieb am Do. 12. Sep. 2019 um
20:51:

Same error here after removing cypress from the package file. But I can
assure you that it says 'better' 😄

What I was thinking: Does the usual end user need cypress as a package at
all? Wouldn't that be a dev dependency?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/1077?email_source=notifications&email_token=AB5O3UXCJEWH6NC3537CIALQJKFUVA5CNFSM4IVX5JN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6S4LQI#issuecomment-530957761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB5O3UTFE26RWUF2FMYBUULQJKFUVANCNFSM4IVX5JNQ
.

@phanan commented on GitHub (Sep 12, 2019): Cypress is a dev dependency (you can check the package.json file). Spike Shape <notifications@github.com> schrieb am Do. 12. Sep. 2019 um 20:51: > Same error here after removing cypress from the package file. But I can > assure you that it says 'better' 😄 > > What I was thinking: Does the usual end user need cypress as a package at > all? Wouldn't that be a dev dependency? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/1077?email_source=notifications&email_token=AB5O3UXCJEWH6NC3537CIALQJKFUVA5CNFSM4IVX5JN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6S4LQI#issuecomment-530957761>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AB5O3UTFE26RWUF2FMYBUULQJKFUVANCNFSM4IVX5JNQ> > . >

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@glics commented on GitHub (Sep 13, 2019):

Apparently gifsicle module doesn't compile on ARM, or at least on my raspberry.
Here's what I have tried:

gifsicle@3.0.4, which is the one used by default, seems to install but won't have a vendor directory at all in its module folder, resulting in a ENOENT
The 4.0.0 package will compile a /vendor/gifsicle binary but then pops out a "unterminated string" syntax error when used (During the final asset processing phase, will attach output as soon as I can),
The 4.0.1 package will not compile or install, spitting out the same syntax error but this time during its compilation

I think this is slightly offtopic now since this seems to be a gifsicle (or imagemin-gifsicle) issue, I'll try to file an issue with them after replicating the behaviour in a new project and reference this.

Do you think there would be any way to distribute a prebuilt Vue app instead of having to compile it?
I was thinking of building it on my PC and then migrating the database and web app... But I admit I'm not sure if there's anything else involved

Also, should I remove the Cypress mention from the issue title and just mention that the build fails on ARM, since now there seem to be other problems?

@glics commented on GitHub (Sep 13, 2019): Apparently gifsicle module doesn't compile on ARM, or at least on my raspberry. Here's what I have tried: - gifsicle@3.0.4, which is the one used by default, seems to install but won't have a vendor directory at all in its module folder, resulting in a ENOENT - The 4.0.0 package will compile a /vendor/gifsicle binary but then pops out a "unterminated string" syntax error when used (During the final asset processing phase, will attach output as soon as I can), - The 4.0.1 package will not compile or install, spitting out the same syntax error but this time during its compilation I think this is slightly offtopic now since this seems to be a gifsicle (or imagemin-gifsicle) issue, I'll try to file an issue with them after replicating the behaviour in a new project and reference this. Do you think there would be any way to distribute a prebuilt Vue app instead of having to compile it? I was thinking of building it on my PC and then migrating the database and web app... But I admit I'm not sure if there's anything else involved Also, should I remove the Cypress mention from the issue title and just mention that the build fails on ARM, since now there seem to be other problems?

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@phanan commented on GitHub (Sep 13, 2019):

In theory, compiling and then copying the assets from another platform should work. I've never tried that though.

You can also try using Docker, perhaps pulling an existing Koel image and modify the script to cater for the latest version.

For the issue's title, I'm fine either way.

@phanan commented on GitHub (Sep 13, 2019): In theory, compiling and then copying the assets from another platform should work. I've never tried that though. You can also try using Docker, perhaps pulling an existing Koel image and modify the script to cater for the latest version. For the issue's title, I'm fine either way.

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@SailHe commented on GitHub (Nov 30, 2019):

What happens if you remove the cypress dependency from package.json?

it works on my raspberry pi 4B

OS: raspbian buster

@SailHe commented on GitHub (Nov 30, 2019): > > > What happens if you remove the cypress dependency from package.json? it works on my raspberry pi 4B - OS: raspbian buster

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@marcbres commented on GitHub (Dec 11, 2019):

it works on my raspberry pi 4B

I've been able to update also on my raspberry pi by deleting the cypress dependency line on package.json

Thank you!

@marcbres commented on GitHub (Dec 11, 2019): > it works on my raspberry pi 4B I've been able to update also on my raspberry pi by deleting the cypress dependency line on package.json Thank you!

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@Kautenja commented on GitHub (Jan 3, 2020):

converting bars.gif to a png (bars.png) and changing the img tag in resources/assets/js/components/ui/sound-bar.vue to the png hackily resolves the issue with the unsupported GIF package on ARM.

@Kautenja commented on GitHub (Jan 3, 2020): converting bars.gif to a png (bars.png) and changing the img tag in resources/assets/js/components/ui/sound-bar.vue to the png hackily resolves the issue with the unsupported GIF package on ARM.

kerem commented

2026-02-26 02:33:45 +03:00

Author

Owner

@BrookeDot commented on GitHub (Apr 22, 2020):

Lots of great debugging and collaboration in this ticker which is great to see. It sound like Koel does work on newer Raspberry Pi's without cypress. I'm going to go ahead and close this issue but it's great to see new uses and devices running Koel.

@BrookeDot commented on GitHub (Apr 22, 2020): Lots of great debugging and collaboration in this ticker which is great to see. It sound like Koel does work on newer Raspberry Pi's without cypress. I'm going to go ahead and close this issue but it's great to see new uses and devices running Koel.

Rows
Columns

[GH-ISSUE #1077] Installation fails on ARM because Cypress is not available for the platform #629