Fork me on GitHub
#aws
<
2018-11-02
>
richiardiandrea02:11:20

@mj_langford doing the same on azure, all good

valtteri08:11:18

What are the benefits of using shadow-cljs with Node/lambda? Are you running the code through advanced optimizations? Sorry for slight off-topic.

lloydshark11:11:00

@valtteri I agree. I wouldn't have thought there is any need for shadow-cljs when targeting lambda as you can simply package the node_modules directly. Targeting the browser - yeah that's another story.

valtteri11:11:04

I’m just curious if there are some fancy built-in goodies in shadow-cljs for targeting node/lambda. 😉

valtteri11:11:35

Never used it myself yet

lilactown15:11:00

it's not really about node_modules at all. you still need a compiler to take your CLJS code and output JS code

lilactown15:11:13

shadow-cljs has excellent out of the box support for targeting Node.js

lilactown15:11:24

I think it even has an azure target?

lilactown15:11:13

but for AWS I believe you can simply target a node lib and shadow-cljs will do the right things re: not bundling dependencies, optimizing correctly, etc.

richiardiandrea15:11:00

@valtteri yes in our case I contributed a shadow target that compiles things as Azure expect them. One of the nice nice things of shadow are also custom or built in "targets"

richiardiandrea15:11:18

Actually I think it was Thomas mainly who contributed that sorry I had to check - memory is failing 😉

valtteri17:11:08

Good to know that shadow has extensible little ‘ecosystem’. It sounds interesting. Need to find time to look into it some day.

mj_langford19:11:08

@valtteri The advantage of targeting shadow-cljs is finding a community committed to a specific stack so you don't have to handle the node/cljs glue yourself everywhere.