starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-26 09:15:59 +03:00

[GH-ISSUE #726] Error installing koel #519

New issue

Closed

opened 2026-02-26 02:33:26 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @fernandopal on GitHub (Mar 11, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/726

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, 因为我不说中文。

When I run "npm install or sudo npm install" this is the output that I get

`> koel@ postinstall /home/fernandopal/koel
> yarn production

yarn run v1.3.2
$ cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
/home/fernandopal/koel/node_modules/laravel-mix/setup/webpack.config.js:1
(function (exports, require, module, __filename, __dirname) { let path = require('path');
                                                              ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at requireConfig (/home/fernandopal/koel/node_modules/webpack/bin/convert-argv.js:97:18)
    at /home/fernandopal/koel/node_modules/webpack/bin/convert-argv.js:104:17
    at Array.forEach (native)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

npm ERR! Linux 3.16.0
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v4.8.7
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR! koel@ postinstall: `yarn production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the koel@ postinstall script 'yarn production'.
npm ERR! This is most likely a problem with the koel package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     yarn production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs koel
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls koel
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/fernandopal/koel/npm-debug.log`

Originally created by @fernandopal on GitHub (Mar 11, 2018). Original GitHub issue: https://github.com/koel/koel/issues/726 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](https://koel.phanan.net/docs), [Upgrade Guide](https://github.com/phanan/koel/releases), as well as [Troubleshooting](https://koel.phanan.net/docs/#/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, 因为我不说中文。 When I run "npm install or sudo npm install" this is the output that I get ``` `> koel@ postinstall /home/fernandopal/koel > yarn production yarn run v1.3.2 $ cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js /home/fernandopal/koel/node_modules/laravel-mix/setup/webpack.config.js:1 (function (exports, require, module, __filename, __dirname) { let path = require('path'); ^^^ SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:373:25) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at requireConfig (/home/fernandopal/koel/node_modules/webpack/bin/convert-argv.js:97:18) at /home/fernandopal/koel/node_modules/webpack/bin/convert-argv.js:104:17 at Array.forEach (native) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. npm ERR! Linux 3.16.0 npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! node v4.8.7 npm ERR! npm v2.15.11 npm ERR! code ELIFECYCLE npm ERR! koel@ postinstall: `yarn production` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the koel@ postinstall script 'yarn production'. npm ERR! This is most likely a problem with the koel package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! yarn production npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs koel npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm ERR! npm owner ls koel npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/fernandopal/koel/npm-debug.log` ```

kerem closed this issue

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

kerem commented

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

Author

Owner

@phanan commented on GitHub (Mar 11, 2018):

99% sure your Node version is out dated.

@phanan commented on GitHub (Mar 11, 2018): 99% sure your Node version is out dated.

kerem commented

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

Author

Owner

@fernandopal commented on GitHub (Mar 11, 2018):

node version and npm version: https://gyazo.com/b33a96a66cc12e0567378eff32bfa70b

@fernandopal commented on GitHub (Mar 11, 2018): node version and npm version: https://gyazo.com/b33a96a66cc12e0567378eff32bfa70b

kerem commented

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

Author

Owner

@phanan commented on GitHub (Mar 11, 2018):

You claimed to have "read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting," right? Well, one of the first things on the wiki is the Requirements section, and it says "NodeJS latest stable," which I'm sure isn't v4.8.7.

@phanan commented on GitHub (Mar 11, 2018): You claimed to have "read and followed closely the Wiki, Upgrade Guide, as well as Troubleshooting," right? Well, one of the first things on the wiki is the Requirements section, and it says "NodeJS latest stable," which I'm sure isn't v4.8.7.

kerem commented

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

Author

Owner

@fernandopal commented on GitHub (Mar 11, 2018):

I updated nodejs to the latest version, cleaned the npm_modules folder.
Now I get this error when I run npm install:
https://gyazo.com/68677345fb00a61ce77c14a13258f6c0

@fernandopal commented on GitHub (Mar 11, 2018): I updated nodejs to the latest version, cleaned the npm_modules folder. Now I get this error when I run npm install: https://gyazo.com/68677345fb00a61ce77c14a13258f6c0

kerem commented

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

Author

Owner

@phanan commented on GitHub (Mar 11, 2018):

That's because you're not installing from a stable Koel version, but from master, which comes back to your unchecked item:

[ ] Is associated with a version. Or better yet, a commit.

The issue template is there for a purpose, so don't tick away just to have your issue opened.

@phanan commented on GitHub (Mar 11, 2018): That's because you're not installing from a stable Koel version, but from `master`, which comes back to your unchecked item: [ ] Is associated with a version. Or better yet, a commit. The issue template is there for a purpose, so don't tick away just to have your issue opened.

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#519

No description provided.

Rows
Columns