[GH-ISSUE #332] Error when installing koel (NPM EPEERINVALID) #244

Closed
opened 2026-02-26 02:32:34 +03:00 by kerem · 8 comments
Owner

Originally created by @Doxylamin on GitHub (May 19, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/332

Hey there,

i get the following error when trying to install / initialize koel.

Installed NPM Version: 2.15.1
Installed Node Version: v4.4.4
koel-init-log.txt
npm-debug-log.txt

Originally created by @Doxylamin on GitHub (May 19, 2016). Original GitHub issue: https://github.com/koel/koel/issues/332 Hey there, i get the following error when trying to install / initialize koel. Installed NPM Version: 2.15.1 Installed Node Version: v4.4.4 [koel-init-log.txt](https://github.com/phanan/koel/files/273594/koel-init-log.txt) [npm-debug-log.txt](https://github.com/phanan/koel/files/273593/npm-debug-log.txt)
kerem closed this issue 2026-02-26 02:32:34 +03:00
Author
Owner

@Doxylamin commented on GitHub (May 19, 2016):

fixed by changing dependencies to "babel-runtime": "^6.0.0",

<!-- gh-comment-id:220472262 --> @Doxylamin commented on GitHub (May 19, 2016): **fixed by changing dependencies to** `"babel-runtime": "^6.0.0",`
Author
Owner

@My1 commented on GitHub (May 24, 2016):

I will try this at home as well. I have the same problem on my raspberry pi

<!-- gh-comment-id:221255697 --> @My1 commented on GitHub (May 24, 2016): I will try this at home as well. I have the same problem on my raspberry pi
Author
Owner

@My1 commented on GitHub (May 24, 2016):

but may I ask WHERE you changed that? I am an NPM noob.

<!-- gh-comment-id:221257144 --> @My1 commented on GitHub (May 24, 2016): but may I ask WHERE you changed that? I am an NPM noob.
Author
Owner

@0xcaff commented on GitHub (May 24, 2016):

It's was changed in the package.json file. I can't reproduce this error.

<!-- gh-comment-id:221262422 --> @0xcaff commented on GitHub (May 24, 2016): It's was changed in the [`package.json`](https://docs.npmjs.com/files/package.json) file. I can't reproduce this error.
Author
Owner

@My1 commented on GitHub (May 24, 2016):

well I recently setup my rpi with raspbia (debian) jessie installed php7 mysql and node/npm (but node/npm came from their site because the apt-get version is way too low)
and after getting through a ton of errors I finally drove it down to this (along with all the deprecated things which seems to be not directly koel's fault.

<!-- gh-comment-id:221267832 --> @My1 commented on GitHub (May 24, 2016): well I recently setup my rpi with raspbia (debian) jessie installed php7 mysql and node/npm (but node/npm came from their site because the apt-get version is way too low) and after getting through a ton of errors I finally drove it down to this (along with all the deprecated things which seems to be not directly koel's fault.
Author
Owner

@My1 commented on GitHub (May 24, 2016):

well I got another dependency error so I thought I try to get koel to a release version instead of just cloning the latest commit because when people make changes not everything has to fit on each commit.

<!-- gh-comment-id:221396521 --> @My1 commented on GitHub (May 24, 2016): well I got another dependency error so I thought I try to get koel to a release version instead of just cloning the latest commit because when people make changes not everything has to fit on each commit.
Author
Owner

@My1 commented on GitHub (May 26, 2016):

to be exact I get this

npm ERR! peerinvalid The package babel-runtime@5.8.38 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer vueify@8.4.1 wants babel-runtime@^6.0.0

normally

npm WARN unmet dependency /home/my1/koel/node_modules/laravel-elixir-vueify requires babel-runtime@'^5.8.34' but will load
npm WARN unmet dependency /home/my1/koel/node_modules/babel-runtime,
npm WARN unmet dependency which is version 6.9.0

when trying to bump babel

so vueify needs babel runtime 6 but laravel-elixir-vueify wants babel runtime 5.8.34

nice stuff, well no.

<!-- gh-comment-id:221956799 --> @My1 commented on GitHub (May 26, 2016): to be exact I get this ``` npm ERR! peerinvalid The package babel-runtime@5.8.38 does not satisfy its siblings' peerDependencies requirements! npm ERR! peerinvalid Peer vueify@8.4.1 wants babel-runtime@^6.0.0 ``` normally ``` npm WARN unmet dependency /home/my1/koel/node_modules/laravel-elixir-vueify requires babel-runtime@'^5.8.34' but will load npm WARN unmet dependency /home/my1/koel/node_modules/babel-runtime, npm WARN unmet dependency which is version 6.9.0 ``` when trying to bump babel so vueify needs babel runtime 6 but laravel-elixir-vueify wants babel runtime 5.8.34 nice stuff, well no.
Author
Owner

@My1 commented on GitHub (May 28, 2016):

intresting I got a completely different error on my windows machine:
browserify because babel-core was
I just npm-installed it and it went fine, mostly

<!-- gh-comment-id:222332879 --> @My1 commented on GitHub (May 28, 2016): intresting I got a completely different error on my windows machine: browserify because babel-core was I just `npm-install`ed it and it went fine, mostly
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#244
No description provided.