Can you share some cljbuild configuration across all builds instead of duplicating it?

jindrichm: with lein? yes, via profiles: https://github.com/technomancy/leiningen/blob/master/doc/PROFILES.md

@darwin: Yes, with lein. Does cljsbuild merge configuration from profiles and builds based on shared ID?

yes, here is an example how I used it recently: https://github.com/binaryage/cljs-devtools-sample/blob/master/project.clj

the trick is to use map form for :cljsbuild configuration, maps are merged automatically

and vectors in their subtrees get concatenated

Is the top-level :cljsbuild {:builds {}} necessary?

see the comment: prevent https://github.com/emezeske/lein-cljsbuild/issues/413

it is not necessary, just reduces warnings when this project is used in checkouts of other project

So you merge the profiles using custom aliases and with-profile?

yes with with-profiles, aliases are just a sugar for command-line

Cool, thanks for explaining.

warning: unfortunately implicit rules for built-in leiningen profiles are quite complicated, so you should avoid naming your profiles the same way, it leads to unexpected behaviour

also lein with-profiles … pprint is your friend when debugging your setup

hi, is anybody using sourcemaps with nodejs? I can't get them to work

There’s a #C09C8GRLY channel; you might have better luck there.

^ @spacepluk

@akiva, I'm using vim actually but anyways I think it's a problem with cljs

it's only failing in some situations

for example (merge a-map a-js-obj) throws and the error is not sourcemapped

Oh. Hah. I totally misread you. Sorry about that.

np

@spacepluk: source maps work with fine Node.js I use them all the time

@spacepluk: “some situations” is vague, if you have minimal case share it so it can be examined

@dnolen for now it seems to be only that case I mentioned, I'll setup a simple test case tomorrow.

@spacepluk: will definitely want to see a minimal case for this, in general case source maps work great

this is how I develop all my ClojureScript libraries

data only tests via Node.js REPL, ui stuff via devcards

yeah for every other error I'm getting they are working great

maybe I'm doing something wrong, I'll let you know asap

I am trying to port spit+slurp to node and cannot get with-open to work. I am trying to writing the macro in cljc so it can throw a js/error, but I cannot get it to work. https://gist.github.com/anonymous/4e7a7c13167f86d3c67a

I've tried requiring it a bunch of different ways. I think defmacro may work differently in cljc?

Question regarding om.next: How do people deal with read and mutation errors?

To clarify with an example, I'm creating a login dialog. Trying to log in runs a remote mutation. How do people handle the case when that mutation fails due to, for instance, a bad username/password combination?

Do you mutate a :login/error field in the state atom, or do you throw an alert box, or what?

I think om.next's way of dealing with state is good, I'm just confused on how to handle stuff like this. In reagent/re-frame I would normally perform the http request, and then mutate the app state based on the response, so this is new territory for me.

@rhansen: you might want to try asking over in #C06DT2YSY. I don’t have an answer but I’d be interested to hear one.

ahh, didn't know of that channel. Thanks for the heads up

@pat If you are working with macros in bootstrap mode, it may be worth trying with ClojureScript master