what's the release cycle for leiningen, i.e. when will we know when 2.7.2 or 2.8.0 will be released?

Hello - I’m gathering arguments. In your opinion, what are the arguments in favour of using leiningen over boot ?

inertia

@yenda I’d like to write something a bit more inspiring(?) than that. As I don’t personally lean toward leiningen, I thought it fair to ask its users

well we are using lein and the only reason we dont switch is inertia what can I say ¯\(ツ)/¯

by we I mean here in my company and by inertia I mean that it is not an easy decision to switch tools like these

there are other priorities, on personnal projects I use boot

I would also say that it is easier to make a lein plugin

because there isnt really much to understand about it

Figwheel and Dirac are both developed for leiningen. There are ports to boot, but I don't think they're first class

and figwheel is better at error reporting than what you get from boot in my experience

> Figwheel and Dirac are both developed for leiningen. There are ports to boot, but I don't think they're first class (edited) I think for Figwheel that's true. There are more boot-oriented alternatives that do 90% of what Figwheel does. Regarding Dirac I think there is no difference: https://github.com/boot-clj/boot-cljs-devtools

hi. i haven't actually compiled much production js with lein and recently switched to a figwheel based workflow. am i correct in thinking figwheel should be auto-building one js file or do i need to feed it a particular flag to get that? or use "lein cljsbuild" (i'm having an issue with that due to having initially installed lein with brew and hence likely needing to do a fresh manual install since brew hasn't been updated...)? right now the compile js file is a link to several files in the (quite large) out folder, including the one that appears to contain all my code

@sophiago: I think it depends on which build figwheel is using - you can have figwheel autobuild multiple builds, and whether they have one or many files and where they output to depends on the build config

I tend to just use lein cljsbuild min when I need to build my production assets, and have a build with the id min that uses advanced optimizations - the figwheel template includes it by default

well my first thought was to try (start-autobuild) in the repl and it came back nil...not sure what that means

and, yes, i started from a template

well, from my config it seems the file i identified as obviously being my compiled js was...but it has an extension .core

is that normal for figwheel templates?

no wait, sorry

it should be the file with the links

but instead i was looking at one "core.js"

it seems from the config that `min will simply compile everything in my out dir into the one js file, right?

oops, meant that to display as code

I'm not sure exactly how it works on the compile side, but putting (start-autobuild "min") into my figwheel repl starts the autobuild and it builds everything into a single JS file

ah ok, let me try that

if i try running "lein cljsbuild min" i get subtask not found 😕

oh could be quotes

lein cljsbuild once min - I forget the once every single time 🙂

ha. thanks

i always think it's my outdated version. i guess brew is not happening 😕

ah yes. beautiful wall of code

thanks 🙂

You got it working? Great!

yup. simple questions, simple answer

(could have said stupid, trying to be easy on myself. lol)

but as far as brew...not happening right? i need to just do a fresh install sometime when i have a minute?

not sure if you're someone to ask

Nope, I've got lein installed with brew but really have no idea how to use a Mac beyond the basics 🙂 I thought I upgraded leiningen on my Windows machine too, but Cursive still tells me it's the old version... so I think I'm doubly unqualified.

welp, the answer is you probably won't be able to upgrade it on your mac that way

not really a big deal. i probably just caught it at a bad time, like the last stable version on brew