Fork me on GitHub
#helix
<
2020-05-25
>
geraldodev00:05:52

(let [input-params {:type "email"} ] ($ tw/Input {:& input-params}))

geraldodev00:05:19

It's a map already, but $ doesnt know because it's resolved at compile time, so I type it again with {&: input-params}.

lilactown02:05:17

Yep that looks correct

aiba02:05:50

I noticed that helix 0.11 comes with a deps.cljs file. This actually causes weirdness for react-native projects, because we are pinned to the version of react that comes with react-native. For example, the latest react-native (0.62) comes with react 16.11.0. Is there a way to :exclude a dependency from npm-deps so shadow-cljs doesn't automatically install helix's npm-deps? Also, does helix actually require react 16.13? (It seems to work fine with react 16.11).

lilactown03:05:20

Helix should work with any 16.x

👍 4
lilactown03:05:51

Does npm-deps override what’s in your package.json already?

aiba03:05:47

yes, it appears to run npm install for each dep

aiba03:05:22

specifically, it runs npm install --save --save-exact [email protected] [email protected]

aiba03:05:30

OK, i just did another experiment and I think the disconnect is that I have a custom :js-options {:js-package-dirs [...]} path set in shadow-cljs.edn, and shadow-cljs doesn't realize that react and react-refresh are already contained in there. Without setting :js-package-dirs, it doesn't override what's already in the package.json.

aiba03:05:44

So, I think this is an issue for shadow-cljs. Sorry for the noise!

lilactown16:05:22

No worries, that sounds confusing