@weavejester I've followed your advice with slight modification. I created my own module as I need an access to the config (compile paths). Now how can I overwrite :duct.compiler/cljs in the development env?

@lambder I’m not sure I understand the question. You just check to see if :duct.core/environment is :development or :production, and modify things accordingly. May I ask why you want to use lein figwheel over Duct’s integrated Figwheel?

yes, that is one way

but using this example I have a general question

how you can override what modules have done

e.g. in development config I'd like to have :duct.compiler/cljs nil to remove the generated config

is it possible ?

Sure. Modules are designed to defer to the user’s configuration, and if you’re writing your own module you can set it after the cljs module. Or just not include the cljs module at all.

it would be useful if you don't control the module and you'd like to overwrite it

so my prod uses a module which sets the compiler/cljs regardles of the environment

I'd like to shadow it in development

or let me ask differently

are the modules run after the config is read?

The modules are functions that are applied to the configuration after it is read.

ok, got it

They run after any :duct.core/includes are added.

i see.

So there is no way to overwrite what 3rd party modules are doing to your config

You can, just by running after them.

how?

programatically ?

or can i do it declaratively?

You can set a module’s dependencies, making it dependent on there being certain keys in the configuration.

So you can create a module that is dependent on the :duct.module/cljs key already being available, for example.

In the next version of Duct the dependency resolution of modules is improved further, but I’m still working on that.

great

The next version of Duct should be out in a month or two, and uses Integrant’s refs and refsets as the dependency resolution mechanism, instead of a :req key as it is currently.

Here’s some info on the current system: https://github.com/duct-framework/core#modules

May I also enquire why you’re using lein figwheel over the inbuilt figwheel?

@weavejester I'm trying to do something quite similar, but I'm not sure I'm doing it right. I want my module to be run after duct.module/cljs has been run. I'm using :req #{duct.module/cljs} in my init-key multi-method, but when my module function is run, I don't see any of duct.module/cljs keys in the config var. Right now I'm using a dirty hack to achieve what I need: I add a #ig/ref to :duct.module/cljs in my module config map, and then invoke the :duct/module/cljs function myself before running my module's code.

@iarenaza That might be a result of how the modules dependencies are currently worked out. The next version should have much better dependency resolution of modules.

So I guess I'll need to keep the dirty hack for the time being. Thanks anyway for your feedback (and of course for your fantastic work on Duct!)