mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1093] problem with installation #643
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#643
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Adamkaram on GitHub (Sep 29, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/1093
Hey,i need to install koel and i'm following the same instruction from koel documents
but when i excute this command i get this error
Note : i'm sorry it's to long
.
i'm tring every thing like
-yarn install
-npm install --global windows-build-tools
this is my composer.json
and this my package.json
{ "name": "koel", "author": "Phan An <me@phanan.net>", "homepage": "https://koel.phanan.net", "license": "MIT", "description": "A personal music streaming server that works", "keywords": [ "music", "audio", "stream" ], "repository": { "type": "git", "url": "https://github.com/phanan/koel" }, "devDependencies": { "@babel/core": "^7.6.2", "@babel/preset-env": "^7.6.2", "cross-env": "^3.2.3", "cypress": "^3.2.0", "font-awesome": "^4.7.0", "kill-port": "^1.3.2", "laravel-mix": "^1.0.0", "node-sass": "^4.12.0", "resolve-url-loader": "3.1.0", "sass": "^1.22.10", "sass-loader": "^7.3.1", "vue-template-compiler": "^2.6.10", "wait-on": "^3.2.0", "webpack": "^3.6.0", "webpack-node-externals": "^1.6.0" }, "scripts": { "dev": "yarn development", "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js", "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js", "watch-poll": "yarn watch -- --watch-poll", "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js", "cy": "kill-port 8088 && php artisan serve --port=8088 & wait-on http://localhost:8088 && cypress run --browser chrome", "build": "yarn production", "prod": "yarn production", "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js", "build-demo": "cross-env NODE_ENV=demo node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js" }, "dependencies": { "babel-loader": "^8.0.6", "vue-loader": "^15.7.1" } }and in my way to fix it i was faced problem with lenght or something like that so i edit config.json in C:\Users\Adam\AppData\Roaming\Composer to be like this
@phanan commented on GitHub (Oct 5, 2019):
Sorry, but I can't provide support down to the level of OS-specific installation. I'll leave the ticket open in case others can help you.
@navjotjsingh commented on GitHub (Nov 3, 2019):
The issue is that older versions of node-sass and node-gyp are being packaged which are incompatible with Node 12.
Please update them in your distributions to support the latest Node.
@almet commented on GitHub (Nov 4, 2019):
Hi, thanks. I'm having the exact same issue here. Maybe it's that koel doesn't support Node 12 yet. Which version is currently supported?
@almet commented on GitHub (Nov 4, 2019):
It seems to be working with node 10.16.2 though.