starred/koel-koel

Fork 0

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

[GH-ISSUE #385] Koel does not start #280

New issue

Closed

opened 2026-02-26 02:32:40 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 02:32:40 +03:00

Owner

Originally created by @X-Ryl669 on GitHub (Jul 29, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/385

I had issue with main.js not building (parse error), and I solved it by telling browserify to accept ".vue" extensions.

Now, I can php artisan serve, logged on the given port, and I get this in my console:

Failed to mount component: template or render function not defined. (found in anonymous component - use the "name" option for better debugging messages.))

warn() main-de790e1f37.js:21724
lifecycleMixin/Vue.prototype._mount() main-de790e1f37.js:20927
[193]</</Vue.prototype.$mount() main-de790e1f37.js:24159
init() main-de790e1f37.js:21184
createElm() main-de790e1f37.js:22683
patch() main-de790e1f37.js:23031
lifecycleMixin/Vue.prototype._update() main-de790e1f37.js:20954
lifecycleMixin/Vue.prototype._mount/vm._watcher<() main-de790e1f37.js:20933
get() main-de790e1f37.js:20116
Watcher() main-de790e1f37.js:20106
lifecycleMixin/Vue.prototype._mount() main-de790e1f37.js:20932
[193]</</Vue.prototype.$mount() main-de790e1f37.js:24159
initRender() main-de790e1f37.js:21387
initMixin/Vue.prototype._init() main-de790e1f37.js:21668
Vue() main-de790e1f37.js:21706
[197]<() main-de790e1f37.js:24350
s() main-de790e1f37.js:1
e()

Using latest git version (v3.1.1-dirty I guess, node v4.4.7), on Debian linux Jessie (followed the unofficial install guide), by the way, and run gulp (not with --production to get a better backtrace)

It would be better if the warn function threw an exception so I could analyze what failed with the debugger, but I can't set a breakpoint (althrough the main.js.map works fine, for source line mapping) on it, so I can't tell what component failed

Originally created by @X-Ryl669 on GitHub (Jul 29, 2016). Original GitHub issue: https://github.com/koel/koel/issues/385 I had issue with main.js not building (parse error), and I solved it by telling browserify to accept ".vue" extensions. Now, I can `php artisan serve`, logged on the given port, and I get this in my console: ``` Failed to mount component: template or render function not defined. (found in anonymous component - use the "name" option for better debugging messages.)) warn() main-de790e1f37.js:21724 lifecycleMixin/Vue.prototype._mount() main-de790e1f37.js:20927 [193]</</Vue.prototype.$mount() main-de790e1f37.js:24159 init() main-de790e1f37.js:21184 createElm() main-de790e1f37.js:22683 patch() main-de790e1f37.js:23031 lifecycleMixin/Vue.prototype._update() main-de790e1f37.js:20954 lifecycleMixin/Vue.prototype._mount/vm._watcher<() main-de790e1f37.js:20933 get() main-de790e1f37.js:20116 Watcher() main-de790e1f37.js:20106 lifecycleMixin/Vue.prototype._mount() main-de790e1f37.js:20932 [193]</</Vue.prototype.$mount() main-de790e1f37.js:24159 initRender() main-de790e1f37.js:21387 initMixin/Vue.prototype._init() main-de790e1f37.js:21668 Vue() main-de790e1f37.js:21706 [197]<() main-de790e1f37.js:24350 s() main-de790e1f37.js:1 e() ``` Using latest git version (v3.1.1-dirty I guess, node v4.4.7), on Debian linux Jessie (followed the unofficial install guide), by the way, and run `gulp` (not with `--production` to get a better backtrace) It would be better if the warn function threw an exception so I could analyze what failed with the debugger, but I can't set a breakpoint (althrough the main.js.map works fine, for source line mapping) on it, so I can't tell what component failed

kerem closed this issue

2026-02-26 02:32:40 +03:00

kerem commented

2026-02-26 02:32:40 +03:00

Author

Owner

@BernardGoldberger commented on GitHub (Jul 29, 2016):

See https://forum.vuejs.org/topic/4399/vue-2-0-vue-warn-failed-to-mount-component-template-or-render-function-not-defined-found-in-root-instance/3

@BernardGoldberger commented on GitHub (Jul 29, 2016): See https://forum.vuejs.org/topic/4399/vue-2-0-vue-warn-failed-to-mount-component-template-or-render-function-not-defined-found-in-root-instance/3

kerem commented

2026-02-26 02:32:40 +03:00

Author

Owner

@X-Ryl669 commented on GitHub (Jul 31, 2016):

Well, it does not work. I've tried many things:

If not using the require('laravel-elixir-vueify-next');trick in the gulpfile, browserify fails with a parse error (and I can't figure out how to capture the intermediate source from a browserify's transform)
If using the trick above, browserify works, but it seems no template are generated (should they ? and if so, where ?)
Using the former trick, plus changing "import Vue from "vue/dist/vue.js" does not make Koel to appear either (same error: can't find template)

While trying to understand this pile of cards, I figured out that: laravel-elixir-vueify-next only add vueify in the broswerify transform chain. It's already what's done in the original gulpfile.js, so I wondered why it does not work, and figured out I only needed to add vueify in the transform chain twice. This does not make sense at all, but without this, it fails somehow.

Can a generous soul where koel works, post its npm module list & node + npm version, because I'm very close to give up with this project... ?

@X-Ryl669 commented on GitHub (Jul 31, 2016): Well, it does not work. I've tried many things: 1. If not using the `require('laravel-elixir-vueify-next');`trick in the gulpfile, browserify fails with a parse error (and I can't figure out how to capture the intermediate source from a browserify's transform) 2. If using the trick above, browserify works, but it seems no template are generated (should they ? and if so, where ?) 3. Using the former trick, plus changing "import Vue from "vue/dist/vue.js" does not make Koel to appear either (same error: can't find template) While trying to understand this pile of cards, I figured out that: laravel-elixir-vueify-next only add vueify in the broswerify transform chain. It's already what's done in the original gulpfile.js, so I wondered why it does not work, and figured out I only needed to add vueify in the transform chain **twice**. This does not make sense at all, but without this, it fails somehow. Can a generous soul where koel works, post its npm module list & node + npm version, because I'm very close to give up with this project... ?

kerem commented

2026-02-26 02:32:40 +03:00

Author

Owner

@phanan commented on GitHub (Jul 31, 2016):

laravel-elixir-vueify isn't needed. A clean npm install works for me – verified on every machine I have. What's your node/npm version, and on what OS?

@phanan commented on GitHub (Jul 31, 2016): `laravel-elixir-vueify` isn't needed. A clean `npm install` works for me – verified on every machine I have. What's your node/npm version, and on what OS?

kerem commented

2026-02-26 02:32:40 +03:00

Author

Owner

@phanan commented on GitHub (Jul 31, 2016):

Nevermind, I see you've posted the versions on the other issue. Please continue there.

@phanan commented on GitHub (Jul 31, 2016): Nevermind, I see you've posted the versions on the other issue. Please continue there.

kerem referenced this issue

2026-02-26 02:35:48 +03:00

[PR #280] [MERGED] Fix - default sorting track parsing #1202

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

No description provided.

Rows
Columns