mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #748] File /css/app.css not defined in asset manifest. #536
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#536
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 @AdebsAlert on GitHub (May 17, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/748
Hey, thanks for contributing to Koel! To save time for both of us, please make sure these checkboxes are checked before submitting the issue:
All checked? Now also make sure your issue
I get this error after I have cloned koel version v3.7.2, ran composer install, npm install and yarn build.
yarn build shows this errors too

Please, what can I do?
@phanan commented on GitHub (May 17, 2018):
What version of Node/npm/yarn do you use?
@erezschatz commented on GitHub (May 17, 2018):
Same error here on the web-side, my yarn build returns the following:
Also, here are the versions you requested
@phanan commented on GitHub (May 17, 2018):
@erezschatz Same? Your problem is totally different, and it's because you cloned the
masterbranch which uses git-submodule. Please don't take other people's issue for yours.@AdebsAlert commented on GitHub (May 17, 2018):
@phanan
Node - v10.0.0
NPM - v6.0.1
Yarn - v1.6.0
@MichaIng commented on GitHub (May 19, 2018):
@phanan
I/We are trying to install Koel 3.7.2 on Debian, failing with the same terminal error message as TO:
€: I hope the following helps further:
node-sass4.9 is needed in combination with Node 10: https://raw.githubusercontent.com/sass/node-sass/master/.github/ISSUE_TEMPLATE/Bug_report.mdlaravel-mixseems to contain an ownnode-sassinstance.php artisan koel:init, the folder structure withinlaravel-mixmodule changes, containing a CHANGELOG.md which indicates outdated version:@phanan commented on GitHub (May 19, 2018):
@AdebsAlert @MichaIng Super helpful info, thanks! I've noticed some (unrelated) problems with the latest combination of yarn/Node as well. May I ask you guys to give it a try with an older version of Node (like 8.x or 7.x) using something like nvm or n and let me know if the problem persists?
@MichaIng commented on GitHub (May 19, 2018):
@phanan
Btw:
@phanan commented on GitHub (May 19, 2018):
Have you checked this? https://github.com/akveo/nebular/issues/339
2018-05-20 1:43 GMT+02:00 MichaIng notifications@github.com:
@MichaIng commented on GitHub (May 20, 2018):
@phanan
Same with errors after
npm i node-sass@4.8.1, if this is what you meant?@phanan commented on GitHub (May 20, 2018):
I mean what you described (which I’ve not time to test yet) looks exactly
that of the linked issue, so maybe explore in that direction :)
On Sun, 20 May 2018 at 02:19, MichaIng notifications@github.com wrote:
@MichaIng commented on GitHub (May 20, 2018):
@phanan
The issue you linked looks similar but not exactly the same than mine. Different line numbers and functions names and also the workaround didn't work and it should be already fixed as well.
BUT: Tried it with Node 8 on the other system and it works! Koel web UI opens without issue.
I then removed the Koel build environment on the other system and started from scratch, including a version downgrade to Node v8.11.2 before running
php artisan koel:initand it worked without issues as well! I guess the back and forth just broke stuff, sorry for not sorting this out in the first place 😉.So the issue seems indeed an incompatibility in combination with Node 10. I refer to https://github.com/phanan/koel/issues/748#issuecomment-390433548 bottom €, as at least with those
node-sassversions outside and insidelaravel-mixsomething goes wrong and the link clearly states thatnode-sass 4.9is needed in combination withNode 10.@AdebsAlert
Long story short, try:
@phanan commented on GitHub (May 20, 2018):
That’s some amazing debugging right there, thanks! I’ll take a deeper look
when I have time. In short though, Node 10 is really a pain to work with :(
On Sun, 20 May 2018 at 14:30, MichaIng notifications@github.com wrote:
@AdebsAlert commented on GitHub (May 20, 2018):
Thank you @MichaIng it works!
Thank you @phanan for an amazing tool.