[GH-ISSUE #569] Expected usage of Webpack #409

New issue

Closed

opened 2026-02-26 02:33:07 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 02:33:07 +03:00

Owner

Originally created by @X-Ryl669 on GitHub (Apr 10, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/569

I've seen that since version 3.6.0, there's webpack used. I wanted to know what is the expected usage of it.

Typically, I have a need for it and I would like to know if you think the same:

Right now, the javascript code is not php's configurable (you can not disable some part of the javascript code from php, you can only rely on status/config variable to activate the code while mounting, but yet, you still pay the cost of compiling it and sending it to the browser)
It seems Webpack is able to load code asynchronously, so then it would mean that you'd pay the cost only if you use it, and I'm really interested by this feature. That way, the folder browsing feature could be integrated in Koel, and configurable by PHP (that is, you'll still build it, but the config variable from PHP would trigger, or not, loading of the folder browsing code if you want so).
It would then make sense to modularize the application so only part of it would be rebuilt when developping.

Is it your intention too ?

Originally created by @X-Ryl669 on GitHub (Apr 10, 2017). Original GitHub issue: https://github.com/koel/koel/issues/569 I've seen that since version 3.6.0, there's webpack used. I wanted to know what is the expected usage of it. Typically, I have a need for it and I would like to know if you think the same: 1. Right now, the javascript code is not php's configurable (you can not disable some part of the javascript code from php, you can only rely on status/config variable to activate the code while mounting, but yet, you still pay the cost of compiling it and sending it to the browser) 2. It seems Webpack is able to load code asynchronously, so then it would mean that you'd pay the cost only if you use it, and I'm really interested by this feature. That way, the folder browsing feature could be integrated in Koel, and configurable by PHP (that is, you'll still build it, but the config variable from PHP would trigger, or not, loading of the folder browsing code if you want so). 3. It would then make sense to modularize the application so only part of it would be rebuilt when developping. Is it your intention too ?

kerem closed this issue

2026-02-26 02:33:07 +03:00

kerem commented

2026-02-26 02:33:07 +03:00

Author

Owner

@phanan commented on GitHub (Apr 10, 2017):

The switch to Webpack was made simply because of the recent changes in Laravel 5.4, where Elixir/Browserify was replaced by Mix/Webpack. I've always preferred Webpack though, and it will certainly open doors for more possibilities in the future (your ideas above, for an example).

@phanan commented on GitHub (Apr 10, 2017): The switch to Webpack was made simply because of the recent changes in Laravel 5.4, where Elixir/Browserify was replaced by Mix/Webpack. I've always preferred Webpack though, and it will certainly open doors for more possibilities in the future (your ideas above, for an example).

kerem referenced this issue

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

[PR #409] [CLOSED] Populate dotenv to config #1238

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

No description provided.

Rows
Columns