Fork me on GitHub
#cljs-edn
<
2016-06-29
shaunlebron00:06:21

yeah, I’ve been using it lately

shaunlebron00:06:52

haven’t had much time to start marketing the idea more

shaunlebron00:06:37

there were some disagreements about including dependencies in there, but I still think it’s okay for those to be optional

shaunlebron00:06:58

@thheller: you have opinions on cljs.edn?

thheller08:06:06

@shaunlebron: I posted some feedback here

thheller08:06:29

with a proof of concept here

thheller08:06:56

I am terrible at describing things

thheller08:06:26

I went a slightly different direction from your initial proposal

thheller08:06:04

basic idea is to create a few "common" configuration setups that should fit 90% of all builds

thheller08:06:22

ie. a dev setup and a release setup

thheller08:06:58

ah hmm similar to the npm-cljs stuff you have done I guess

thheller08:06:09

didn't see that

shaunlebron14:06:54

@thheller: sorry I missed that issue somehow..

shaunlebron15:06:02

i’ll have to look at the example soon so I can give you more feedback

shaunlebron15:06:19

i do like the three points you made in the issue though