I am planning to create a module that adds support for webpack to Clojurescript. In some cases, it is required for packaging an app that uses dependencies that shadow_cljs can't handle. One example would be Ionic framework, as explained in this post, which doesn't work properly without webpack.
It can be implementing either as a separate profile on :kit/cljs module, or a separate module that builds on it, e.g :kit/webpack. I tend to prefer the second option, since in that case, the decision can be delayed until it's needed later in development.
Btw, it's a little bit confusing if we should file modules related tickets here, or in modules project. For me, it make sense here, since modules belong to kit project? In that case, you might want to disable tickets in modules project and add a Readme with a short note about it?
I am planning to create a module that adds support for webpack to Clojurescript. In some cases, it is required for packaging an app that uses dependencies that shadow_cljs can't handle. One example would be Ionic framework, as explained in this post, which doesn't work properly without webpack.
It can be implementing either as a separate profile on
:kit/cljs
module, or a separate module that builds on it, e.g:kit/webpack
. I tend to prefer the second option, since in that case, the decision can be delayed until it's needed later in development.Btw, it's a little bit confusing if we should file modules related tickets here, or in modules project. For me, it make sense here, since modules belong to kit project? In that case, you might want to disable tickets in modules project and add a Readme with a short note about it?