If :build-defaults sets an option, it would be great to be able to unset or remove said option in some builds. The configs are overridden using deep-merge which is additive. I know we could pass that value to the build directly instead of having it in the defaults (whitelisting instead of blacklisting), but if the value is a big map (ex :js-options) and because EDN doesn't have variables or refs, it would be a lot of code duplication. Alternatively, it would be great if you could have the option to have a shadow-cljs.clj instead of the edn that would produce the final config map (kind of like webpack.json vs webpack.js).
If :build-defaults sets an option, it would be great to be able to unset or remove said option in some builds. The configs are overridden using deep-merge which is additive. I know we could pass that value to the build directly instead of having it in the defaults (whitelisting instead of blacklisting), but if the value is a big map (ex :js-options) and because EDN doesn't have variables or refs, it would be a lot of code duplication. Alternatively, it would be great if you could have the option to have a shadow-cljs.clj instead of the edn that would produce the final config map (kind of like webpack.json vs webpack.js).