Fork me on GitHub
#shadow-cljs
<
2019-03-05
>
flyboarder04:03:46

boot-shadow has been updated to use shadow-cljs 2.8.14

flyboarder04:03:01

@thheller smoothest update to the boot task yet, shadow is great!

👍 4
biscuitpants12:03:13

ignoring obvious security holes, would it be possible to run a shadow-cljs build server on an AWS instance, and connect to the cljs-repl that is exposed? such that you can hot load CLJS code from a remote repl

thheller14:03:01

@biscuitpants sure but lots of the assumptions build into the system is that files are loaded locally from disk

thheller14:03:56

so loading them purely over the REPL may not work properly

biscuitpants15:03:45

hmm okay, and if we had all the source on disk too? so we are only compiling new code into an existing project

biscuitpants15:03:54

so process would be: git checkout develop of our project -> start shadow build -> connect via remote repl and switch to cljs and compile

biscuitpants15:03:17

to test i guess its just a matter of running shadow and opening the port it listens on, eh?

tomc20:03:27

I'm trying to convert a figwheel-based cljs project to shadow-cljs so that I can compare the dev experience. I have a javascript library (not from npm) under :foreign-libs in my figwheel config. How do I translate that to shadow-cljs?

thheller20:03:23

what kind of javascript lib?

thheller20:03:35

commonjs? es6?

tomc20:03:18

neither, it just defines a function in the global scope

thheller20:03:58

does it have a goog.provide?

thheller20:03:01

basically you can skip all the foreign-lib stuff and just require the file directly

tomc20:03:12

Looks like this is exactly what I need. Thank you.

tomc20:03:00

Great work on the shadow-cljs docs by the way. Nice to use a clojure project that holds the user's hand a bit.

😎 1