[GH-ISSUE #748] File /css/app.css not defined in asset manifest. #536

Closed
opened 2026-02-26 02:33:29 +03:00 by kerem · 13 comments
Owner

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:

  • [-] 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, 因为我不说中文。
screen shot 2018-05-17 at 12 13 28 pm

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
screen shot 2018-05-17 at 12 18 01 pm

Please, what can I do?

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: - [-] 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, 因为我不说中文。 <img width="1094" alt="screen shot 2018-05-17 at 12 13 28 pm" src="https://user-images.githubusercontent.com/6014431/40174139-08ac26d8-59cc-11e8-8b13-b8057060762f.png"> 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 <img width="563" alt="screen shot 2018-05-17 at 12 18 01 pm" src="https://user-images.githubusercontent.com/6014431/40174261-6b9e9ff0-59cc-11e8-8539-93968c8fe0ea.png"> Please, what can I do?
kerem closed this issue 2026-02-26 02:33:29 +03:00
Author
Owner

@phanan commented on GitHub (May 17, 2018):

What version of Node/npm/yarn do you use?

<!-- gh-comment-id:389873270 --> @phanan commented on GitHub (May 17, 2018): What version of Node/npm/yarn do you use?
Author
Owner

@erezschatz commented on GitHub (May 17, 2018):

Same error here on the web-side, my yarn build returns the following:

 ERROR  Failed to compile with 4 errors                               2:19:43 PM

These dependencies were not found:

* /var/www/html/koel/resources/assets/js/app.js in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss
* /var/www/html/koel/resources/assets/js/remote/app.js in multi ./resources/assets/js/remote/app.js
* /var/www/html/koel/resources/assets/sass/app.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss
* /var/www/html/koel/resources/assets/sass/remote.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss

To install them, you can run: npm install --save /var/www/html/koel/resources/assets/js/app.js /var/www/html/koel/resources/assets/js/remote/app.js /var/www/html/koel/resources/assets/sass/app.scss /var/www/html/koel/resources/assets/sass/remote.scss

Also, here are the versions you requested

$ node -v
v8.10.0
$ npm -v
3.5.2
$ yarn -v
1.6.0
<!-- gh-comment-id:389883078 --> @erezschatz commented on GitHub (May 17, 2018): Same error here on the web-side, my yarn build returns the following: ``` ERROR Failed to compile with 4 errors 2:19:43 PM These dependencies were not found: * /var/www/html/koel/resources/assets/js/app.js in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss * /var/www/html/koel/resources/assets/js/remote/app.js in multi ./resources/assets/js/remote/app.js * /var/www/html/koel/resources/assets/sass/app.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss * /var/www/html/koel/resources/assets/sass/remote.scss in multi ./resources/assets/js/app.js ./resources/assets/sass/app.scss ./resources/assets/sass/remote.scss To install them, you can run: npm install --save /var/www/html/koel/resources/assets/js/app.js /var/www/html/koel/resources/assets/js/remote/app.js /var/www/html/koel/resources/assets/sass/app.scss /var/www/html/koel/resources/assets/sass/remote.scss ``` Also, here are the versions you requested ``` $ node -v v8.10.0 $ npm -v 3.5.2 $ yarn -v 1.6.0 ```
Author
Owner

@phanan commented on GitHub (May 17, 2018):

@erezschatz Same? Your problem is totally different, and it's because you cloned the master branch which uses git-submodule. Please don't take other people's issue for yours.

<!-- gh-comment-id:389887230 --> @phanan commented on GitHub (May 17, 2018): @erezschatz Same? Your problem is totally different, and it's because you cloned the `master` branch which uses git-submodule. Please don't take other people's issue for yours.
Author
Owner

@AdebsAlert commented on GitHub (May 17, 2018):

@phanan
Node - v10.0.0
NPM - v6.0.1
Yarn - v1.6.0

<!-- gh-comment-id:389897360 --> @AdebsAlert commented on GitHub (May 17, 2018): @phanan Node - v10.0.0 NPM - v6.0.1 Yarn - v1.6.0
Author
Owner

@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:

...
In file included from ../src/binding.cpp:1:0:
../../nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’:
../../nan/nan.h:865:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
         v8::Isolate::GetCurrent(), target, method, argc, argv);
                                                              ^
In file included from ../../nan/nan.h:49:0,
                 from ../src/binding.cpp:1:
/root/.node-gyp/10.1.0/include/node/node.h:158:50: note: declared here
                 NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                  ^
/root/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
     __attribute__((deprecated(message))) declarator
                                          ^~~~~~~~~~
In file included from ../src/binding.cpp:1:0:
../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::Callback::Call_(v8::Isolate*, v8::Local<v8::Object>, int, v8::Local<v8::Value>*) const’:
../../nan/nan.h:1479:5: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
     ));
     ^
In file included from ../../nan/nan.h:49:0,
                 from ../src/binding.cpp:1:
/root/.node-gyp/10.1.0/include/node/node.h:172:50: note: declared here
                 NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                  ^
/root/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
     __attribute__((deprecated(message))) declarator
                                          ^~~~~~~~~~
binding.target.mk:115: recipe for target 'Release/obj.target/binding/src/binding.o' failed
make: Leaving directory '/var/www/koel/node_modules/node-sass/build'
make: *** [Release/obj.target/binding/src/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/var/www/koel/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
gyp ERR! System Linux 4.16.0-1-amd64
gyp ERR! command "/usr/local/bin/node" "/var/www/koel/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /var/www/koel/node_modules/node-sass
gyp ERR! node -v v10.1.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

€: I hope the following helps further:

root@DietPi:/var/www/koel# npm ls node-sass
koel@ /var/www/koel
├─┬ laravel-mix@0.8.9
│ └── node-sass@4.9.0  deduped
└── node-sass@4.9.0
  • After php artisan koel:init, the folder structure within laravel-mix module changes, containing a CHANGELOG.md which indicates outdated version:
root@DietPi:/var/www/koel# cat node_modules/laravel-mix/node_modules/node-sass/CHANGELOG.md
## v4.5.0
<!-- gh-comment-id:390433548 --> @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: ``` ... In file included from ../src/binding.cpp:1:0: ../../nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’: ../../nan/nan.h:865:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations] v8::Isolate::GetCurrent(), target, method, argc, argv); ^ In file included from ../../nan/nan.h:49:0, from ../src/binding.cpp:1: /root/.node-gyp/10.1.0/include/node/node.h:158:50: note: declared here NODE_EXTERN v8::Local<v8::Value> MakeCallback( ^ /root/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’ __attribute__((deprecated(message))) declarator ^~~~~~~~~~ In file included from ../src/binding.cpp:1:0: ../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::Callback::Call_(v8::Isolate*, v8::Local<v8::Object>, int, v8::Local<v8::Value>*) const’: ../../nan/nan.h:1479:5: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations] )); ^ In file included from ../../nan/nan.h:49:0, from ../src/binding.cpp:1: /root/.node-gyp/10.1.0/include/node/node.h:172:50: note: declared here NODE_EXTERN v8::Local<v8::Value> MakeCallback( ^ /root/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’ __attribute__((deprecated(message))) declarator ^~~~~~~~~~ binding.target.mk:115: recipe for target 'Release/obj.target/binding/src/binding.o' failed make: Leaving directory '/var/www/koel/node_modules/node-sass/build' make: *** [Release/obj.target/binding/src/binding.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/var/www/koel/node_modules/node-gyp/lib/build.js:258:23) gyp ERR! stack at ChildProcess.emit (events.js:182:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12) gyp ERR! System Linux 4.16.0-1-amd64 gyp ERR! command "/usr/local/bin/node" "/var/www/koel/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" gyp ERR! cwd /var/www/koel/node_modules/node-sass gyp ERR! node -v v10.1.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok Build failed with error code: 1 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ``` - Warnings start a lot of lines earlier, not sure which one is helpful. - We tried it on Stretch as well as Buster. - We found the following issues, that seem to be related, maybe this helps: - https://github.com/sass/node-sass/issues/1781#issuecomment-258069797 - https://github.com/yarnpkg/yarn/issues/1632 **€: I hope the following helps further:** - Might have something to do with the fact that `node-sass` 4.9 is needed in combination with Node 10: https://raw.githubusercontent.com/sass/node-sass/master/.github/ISSUE_TEMPLATE/Bug_report.md - `laravel-mix` seems to contain an own `node-sass` instance. - When I do any npm update/install, both versions are up-to-date: ``` root@DietPi:/var/www/koel# npm ls node-sass koel@ /var/www/koel ├─┬ laravel-mix@0.8.9 │ └── node-sass@4.9.0 deduped └── node-sass@4.9.0 ``` - After `php artisan koel:init`, the folder structure within `laravel-mix` module changes, containing a CHANGELOG.md which indicates outdated version: ``` root@DietPi:/var/www/koel# cat node_modules/laravel-mix/node_modules/node-sass/CHANGELOG.md ## v4.5.0 ```
Author
Owner

@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?

<!-- gh-comment-id:390439305 --> @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?
Author
Owner

@MichaIng commented on GitHub (May 19, 2018):

@phanan

  • With version 8 indeed the error does not appear any more, but I face different ones then:
root@DietPi:~# npm install -g n
/usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n
+ n@2.1.11
added 1 package from 4 contributors in 2.118s
root@DietPi:~# n 8

     install : node-v8.11.2
       mkdir : /usr/local/n/versions/node/8.11.2
       fetch : https://nodejs.org/dist/v8.11.2/node-v8.11.2-linux-x64.tar.gz
######################################################################################################################################################### 100.0%
   installed : v8.11.2

root@DietPi:~# cd /var/www/koel/
root@DietPi:/var/www/koel# php artisan koel:init
Attempting to install or upgrade Koel.
Remember, you can always install/upgrade manually following the guide here:
📙  https://koel.phanan.net/docs

App key exists -- skipping
JWT secret exists -- skipping
Migrating database
Data seeded -- skipping
Compiling front-end stuff
yarn install v1.6.0
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.1.2: The platform "linux" is incompatible with this module.
info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ yarn production
yarn run v1.6.0
$ 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 errors01:33:30

 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 /var/www/koel/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-1ce16e40","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
....
  • Several similar module build errors appear, I guess the 47 mentioned ones.
  • See also my edit (€) above about node-sass, as also this error contains sass.

Btw:

root@DietPi:/var/www/koel# node -v
v8.11.2
root@DietPi:/var/www/koel# npm -v
5.6.0
<!-- gh-comment-id:390440779 --> @MichaIng commented on GitHub (May 19, 2018): @phanan - With version 8 indeed the error does not appear any more, but I face different ones then: ``` root@DietPi:~# npm install -g n /usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n + n@2.1.11 added 1 package from 4 contributors in 2.118s root@DietPi:~# n 8 install : node-v8.11.2 mkdir : /usr/local/n/versions/node/8.11.2 fetch : https://nodejs.org/dist/v8.11.2/node-v8.11.2-linux-x64.tar.gz ######################################################################################################################################################### 100.0% installed : v8.11.2 root@DietPi:~# cd /var/www/koel/ root@DietPi:/var/www/koel# php artisan koel:init Attempting to install or upgrade Koel. Remember, you can always install/upgrade manually following the guide here: 📙 https://koel.phanan.net/docs App key exists -- skipping JWT secret exists -- skipping Migrating database Data seeded -- skipping Compiling front-end stuff yarn install v1.6.0 [1/4] Resolving packages... [2/4] Fetching packages... info fsevents@1.1.2: The platform "linux" is incompatible with this module. info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh packages... success Saved lockfile. $ yarn production yarn run v1.6.0 $ 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 errors01:33:30 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 /var/www/koel/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-1ce16e40","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 .... ``` - Several similar module build errors appear, I guess the 47 mentioned ones. - See also my edit (€) above about node-sass, as also this error contains sass. Btw: ``` root@DietPi:/var/www/koel# node -v v8.11.2 root@DietPi:/var/www/koel# npm -v 5.6.0 ```
Author
Owner

@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:

@phanan https://github.com/phanan

  • With version 8 indeed the error does not appear any more, but I face
    different ones then:

root@DietPi:~# npm install -g n
/usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n

  • n@2.1.11
    added 1 package from 4 contributors in 2.118s
    root@DietPi:~# n 8

    install : node-v8.11.2
    mkdir : /usr/local/n/versions/node/8.11.2
    fetch : https://nodejs.org/dist/v8.11.2/node-v8.11.2-linux-x64.tar.gz
    ######################################################################################################################################################### 100.0%
    installed : v8.11.2

root@DietPi:~# cd /var/www/koel/
root@DietPi:/var/www/koel# php artisan koel:init
Attempting to install or upgrade Koel.
Remember, you can always install/upgrade manually following the guide here:
📙 https://koel.phanan.net/docs

App key exists -- skipping
JWT secret exists -- skipping
Migrating database
Data seeded -- skipping
Compiling front-end stuff
yarn install v1.6.0
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.1.2: The platform "linux" is incompatible with this module.
info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
$ yarn production
yarn run v1.6.0
$ 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 errors01:33:30

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 /var/www/koel/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-1ce16e40","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
....

  • Several similar module build errors appear, I guess the 47 mentioned
    ones.
  • See also my edit (€) above about node-sass, as also this error
    contains sass.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/748#issuecomment-390440779, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0l2BjEEqGtkwpvIBrihnHamncBynks5t0K4fgaJpZM4UC4Il
.

<!-- gh-comment-id:390441031 --> @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>: > @phanan <https://github.com/phanan> > > - With version 8 indeed the error does not appear any more, but I face > different ones then: > > root@DietPi:~# npm install -g n > /usr/local/bin/n -> /usr/local/lib/node_modules/n/bin/n > + n@2.1.11 > added 1 package from 4 contributors in 2.118s > root@DietPi:~# n 8 > > install : node-v8.11.2 > mkdir : /usr/local/n/versions/node/8.11.2 > fetch : https://nodejs.org/dist/v8.11.2/node-v8.11.2-linux-x64.tar.gz > ######################################################################################################################################################### 100.0% > installed : v8.11.2 > > root@DietPi:~# cd /var/www/koel/ > root@DietPi:/var/www/koel# php artisan koel:init > Attempting to install or upgrade Koel. > Remember, you can always install/upgrade manually following the guide here: > 📙 https://koel.phanan.net/docs > > App key exists -- skipping > JWT secret exists -- skipping > Migrating database > Data seeded -- skipping > Compiling front-end stuff > yarn install v1.6.0 > [1/4] Resolving packages... > [2/4] Fetching packages... > info fsevents@1.1.2: The platform "linux" is incompatible with this module. > info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation. > [3/4] Linking dependencies... > [4/4] Building fresh packages... > success Saved lockfile. > $ yarn production > yarn run v1.6.0 > $ 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 errors01:33:30 > > 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 /var/www/koel/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-1ce16e40","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 > .... > > > - Several similar module build errors appear, I guess the 47 mentioned > ones. > - See also my edit (€) above about node-sass, as also this error > contains sass. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/748#issuecomment-390440779>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0l2BjEEqGtkwpvIBrihnHamncBynks5t0K4fgaJpZM4UC4Il> > . >
Author
Owner

@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?

<!-- gh-comment-id:390443379 --> @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?
Author
Owner

@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:

@phanan https://github.com/phanan
Same with errors after npm i node-sass@4.8.1, if this is what you meant?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/748#issuecomment-390443379, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0sXvxG0i93RMO9NxIohc9PN7gNlEks5t0LaCgaJpZM4UC4Il
.

<!-- gh-comment-id:390461506 --> @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: > @phanan <https://github.com/phanan> > Same with errors after npm i node-sass@4.8.1, if this is what you meant? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/748#issuecomment-390443379>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0sXvxG0i93RMO9NxIohc9PN7gNlEks5t0LaCgaJpZM4UC4Il> > . >
Author
Owner

@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:init and 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-sass versions outside and inside laravel-mix something goes wrong and the link clearly states that node-sass 4.9 is needed in combination with Node 10.

@AdebsAlert
Long story short, try:

npm install -g n
n 8
php artisan koel:init
<!-- gh-comment-id:390477430 --> @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:init` and 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-sass` versions outside and inside `laravel-mix` something goes wrong and the link clearly states that `node-sass 4.9` is needed in combination with `Node 10`. @AdebsAlert Long story short, try: ``` npm install -g n n 8 php artisan koel:init ```
Author
Owner

@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:

@phanan https://github.com/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:init and it worked without issues as well!

So the issue is indeed an incompatibility in combination with Node 10. I
refer to #748 (comment)
https://github.com/phanan/koel/issues/748#issuecomment-390433548 bottom
€, as at least with those node-sass versions outside and inside
laravel-mix something goes wrong and the link clearly states that node-sass
4.9 is needed in combination with Node 10.

@AdebsAlert https://github.com/AdebsAlert
Long story short, try:

npm install -g n
n 8
php artisan koel:init


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/748#issuecomment-390477430, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0hx12maGLqro1PQhMA2gfCjFYj1kks5t0WHngaJpZM4UC4Il
.

<!-- gh-comment-id:390478786 --> @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: > @phanan <https://github.com/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:init and it worked without issues as well! > > So the issue is indeed an incompatibility in combination with Node 10. I > refer to #748 (comment) > <https://github.com/phanan/koel/issues/748#issuecomment-390433548> bottom > €, as at least with those node-sass versions outside and inside > laravel-mix something goes wrong and the link clearly states that node-sass > 4.9 is needed in combination with Node 10. > > @AdebsAlert <https://github.com/AdebsAlert> > Long story short, try: > > npm install -g n > n 8 > php artisan koel:init > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/phanan/koel/issues/748#issuecomment-390477430>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AHrt0hx12maGLqro1PQhMA2gfCjFYj1kks5t0WHngaJpZM4UC4Il> > . >
Author
Owner

@AdebsAlert commented on GitHub (May 20, 2018):

Thank you @MichaIng it works!

Thank you @phanan for an amazing tool.

<!-- gh-comment-id:390490019 --> @AdebsAlert commented on GitHub (May 20, 2018): Thank you @MichaIng it works! Thank you @phanan for an amazing tool.
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#536
No description provided.