mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #765] Mixins Issues #552
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#552
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 @sajeeshen on GitHub (Jul 14, 2018).
Original GitHub issue: https://github.com/koel/koel/issues/765
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
@sajeeshen commented on GitHub (Jul 14, 2018):
I have installed Koel, but I am getting some strange error
Here I am pasting the error
cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
95% emitting ERROR Failed to compile with 47 errors21:58:17
error in ./resources/assets/js/components/main-wrapper/main-content/artist.vue
Module build failed:
@mixin control($playBtnWidth, $fontSize, $textIndent) {
^
Mixins may not be defined within control directives or other mixins.
in /Applications/XAMPP/xamppfiles/htdocs/resources/assets/sass/partials/_mixins.scss (line 79, column 14)
@ ./node_modules/vue-style-loader!./node_modules/css-loader!./node_modules/vue-loader/lib/style-compiler?{"vue":true,"id":"data-v-257ebd9c","scoped":true,"hasInlineConfig":true}!./node_modules/sass-loader/lib/loader.js!./node_modules/vue-loader/lib/selector.js?type=styles&index=0!./resources/assets/js/components/main-wrapper/main-content/artist.vue 4:14-378
@ ./resources/assets/js/components/main-wrapper/main-content/artist.vue
@ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":"es2015",{"modules":false}}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/main-wrapper/main-content/index.vue
@ ./resources/assets/js/components/main-wrapper/main-content/index.vue
@ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":"es2015",{"modules":false}}!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./resources/assets/js/components/main-wrapper/index.vue
@ ./resources/assets/js/components/main-wrapper/index.vue
@ ./node_modules/babel-loader/lib?{"cacheDirectory":true,"presets":"es2015",{"modules":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
error in ./resources/assets/sass/app.scss
@dcschmid commented on GitHub (Jul 17, 2018):
I have the same Problem. I thhink node-sass is not correctly installed. I installeed it on freebsd and there is the problem node-sass can not really build. Is there a way to get the build assets. A complete Release would be great, so someone can be Download a zip and extracted it and koel runs automaticly with out build assets and so on.
@amadeann commented on GitHub (Aug 3, 2018):
There is a problem with
node-sassversion. I found that with version4.7.2assets compile without a problem. The project requires^4.7.2, and in my case (probably yours as well) installs4.9.2.To fix it, change
"node-sass": "^4.7.2",to"node-sass": "~4.7.2",in yourpackage.json. Runyarn install, and you shouldn't see any errors.I also noticed that when you run
yarn installon the core repository, which has exactly samenode-sassversion requirement (i.e.^4.7.2), version4.7.2(not4.9.2) is installed.@yuis-ice commented on GitHub (Jun 4, 2021):
I have the similar issue and couldn't solve the issue with changing
"node-sass": "^4.13.1"to"node-sass": "~4.13.1". wtf