Fork me on GitHub
#boot
<
2015-08-14
>
pandeiro01:08:23

Does boot-reload :ids take #{"main"} <-- like this for e.g. main.cljs.edn ?

pandeiro01:08:48

that doesn't work as expected here

pandeiro01:08:43

ah i think maybe the current snapshot is != master

pandeiro01:08:34

So boot-cljs master, when it's building multiple .cljs.edn, the resulting .js files for each build all refer to main.out/path/to/assets

pandeiro01:08:51

rather than their respective <foo>.out/path/etc

pandeiro01:08:18

...that's because i'm specifying that in one (cljs ...) task that builds everything...

pandeiro01:08:36

but how could i do anything different there?

pandeiro01:08:10

ok so in my case, i can get by without using :compiler-options {:asset-path ... }, and everything just works (yay)

tel01:08:44

Is there an example repo anywhere around of, say, boot reload, cljs, less?

tel01:08:13

and cljs.test simple_smile

pandeiro02:08:04

@tel: i'm updating an older example now as well

tel03:08:30

pandeiro: sweet!

onetom03:08:36

@pandeiro: sounds awesome indeed

tel13:08:42

ohhhhhhhhhh

tel13:08:51

I see how people are doing cljs tests

tel13:08:04

that’s clever

tel13:08:37

just having their own .edn target

micha13:08:11

@pandeiro: very nice work

micha13:08:15

!m pandeiro

pandeiro13:08:41

@tel: that's one way, the easiest imo... the other route is to get fancy and define a task that generates that .cljs.edn file

tel13:08:17

I guess I should say “I see how @pandeiro is doing cljs testing"

pandeiro13:08:18

@micha: thanks, i finally figured out using with-pre-wrap and with-post-wrap to do what i wanted -- i may be able to publish that work soon

pandeiro13:08:49

but the approach in jamal is dead simple and works pretty well if your development is browser-based

tel13:08:17

it’s perfect

tel13:08:37

thanks 😄

tel15:08:37

Anyone using cljs-repl and vim fireplace?

tel15:08:48

I’m running into errors getting set up

tel15:08:38

even (start-repl) is failing with a Piggieback error

tel15:08:18

rather a weasel one

tel15:08:20

java.lang.IllegalArgumentException: No value supplied for key: [email protected]

pandeiro18:08:33

are .cljs.cache files a clojurescript thing or boot-cljs thing?

pandeiro18:08:09

Hitting the stale tests thing again, even with .cljs.edn files specifying :init-fns

pandeiro20:08:00

Why would (sift :include #{#"(^index\.html$|^.+\.js$|^styles.css$)"}) NOT eliminate the various *.out/ dirs created in cljs compilation? (And are those dirs even supposed to be created with :advanced?)

micha20:08:19

if you want to remove things you can use the :invert option to sift to exclude things, like this

micha20:08:55

(sift :invert true :include #{#"\.out/"})

pandeiro20:08:25

@micha: ok right... i can't just :include a regex and filter based on that?

micha20:08:32

and also we need to remove those dirs in the task when source maps are not enabled and optimizations are on

micha20:08:38

no, you can

pandeiro20:08:13

yeah so that's why i'm puzzled my regex isn't working to remove those...

pandeiro20:08:44

and even with source maps, the *.out/s shouldn't be needed right?

micha20:08:55

source maps needs the output dir

pandeiro20:08:57

there should just be a single main.js.map or something no?

micha20:08:09

no, it uses the original cljs namespace files

micha20:08:18

which are in the out dir

pandeiro20:08:31

right yeah ok, makes sense

pandeiro20:08:45

does the sift behavior i'm seeing sound right to you?

micha20:08:53

seems like a bug

micha20:08:13

i'm not a regex expert

micha20:08:26

so maybe test in the repl if the regex is doing what you think it's doing

pandeiro20:08:39

yeah very weird behavior

pandeiro20:08:53

should i be able to use two different sift tasks in the same pipeline?

micha20:08:15

does the regex work the way you expect when you test it with just a string?

pandeiro20:08:44

i mean now i'm getting weirdness even testing stuff like #{#"index"} -- which is causing the entire target directory to disappear simple_smile

pandeiro20:08:57

(within a final sift task i mean)

micha20:08:11

do you have symlinks in there?

pandeiro20:08:17

none at all

micha20:08:18

i mean it should be safe but you never knwo

pandeiro20:08:46

yeah no this is very haywire, i think i'm gonna need to put the crackpipe down even

alandipert20:08:56

that’s a good start

micha20:08:56

don't be hasty

micha20:08:18

we need to rewrite the sift thing using reducers

alandipert20:08:19

micha swears by crack, i’m more into coffee

pandeiro20:08:34

some people swear by sleep too...

micha20:08:41

sleep is a crutch

pandeiro20:08:45

yeah totally

micha20:08:58

crack is more like a prosthetic limb

micha20:08:14

or maybe a phantom limb

pandeiro20:08:21

hey something i meant to ask you guys a while back

pandeiro20:08:31

was the sound just very bad on the video recording of the boot presentation?

pandeiro20:08:37

or was that the crack?

alandipert20:08:23

the sound was not excellent, i remember some last minute shenanigan about there not being enough lapel mics

pandeiro20:08:13

ok, yeah i was able to hear parts of it but it was a struggle... i was kind of hoping maybe someone had fixed it somehow with post-processing

alandipert20:08:34

we should do a rifftrack

pandeiro20:08:48

i don't know what that is but it sounds awesome

alandipert20:08:01

a comedic dubb of a b-movie you can find on the internet

pandeiro20:08:13

oh yeah for sure

pandeiro20:08:35

have people done that before on tech presentations?

alandipert20:08:52

not that i know of

pandeiro20:08:20

another pioneering moment; this project is truly on hallowed ground