@jetzajac: I had a task like that in mind, I wrote boot-exec to ease writing shell commands with boot

https://github.com/degree9/boot-exec

@jetzajac: I could really use that as well for boot-react-native

@flyboarder: boot-exec looks neat! can it call processes in the background?

the other problem is that with npm it's not really feasible to re-install everything on every boot run, as it takes too long, so the npm directory cannot be a tmp-dir

@pesterhazy: it is not smart enough to handle background proc’s and assumes you want to wait for execution, also with boot-exec you can pass a :directory this can be a cache directory created by the npm wrapper task, a similar thing is done with boot-bower

https://github.com/degree9/boot-bower/blob/master/src/degree9/boot_bower.clj#L22-L23

oh wow, I didn't know you could use boot's cache from boot modules

so many possibilities 🙂

Hi y'all, I'm pretty much brand new to boot, long-time lein user. Is there a way to do what vinyasa does in lein, ie inject code into clojure.core so that it'll be loaded in every namespace? (eg requiring pprint) Vinyasa: https://github.com/zcaudate/vinyasa

(in the REPL, that is, not in production)

@eggsyntax: it couldn't be easier

(intern (the-ns 'clojure.core) 'foop 100)

you can put that in your profile.boot file

for instance

Ah, that is easy. Thanks!

all boot does is get you to the point where you can program in clojure

from there you can do anything

:thumbsup: 🙂

there is also a file that boot looks for, boot-shim.clj

in the ~/.boot directory and in the project dir

that will be evaluated in every pod

you can use that to modify clojure itself

or to add your "injections" etc

Cool, I'll look into that as well.

@eggsyntax: if you do boot -vb task task you can see the namespace boot generates

might help you see what's exactly going on

that generated namespace is the only magical part of the bootstrapping process

Excellent, thanks so much 🙂

👍 have fun!

how is this :boot/from ns meta used? https://github.com/boot-clj/boot/blob/master/boot/pod/src/boot/from/me/raynes/conch.clj#L9

iirc it's just a comment currently

👌

is there a way in boot to launch a REPL in the environment of the build itself?:

e.g. to inspect settings, etc.

@spieden: not sure what you mean by the build itself?

well, for example i’m trying to debug "missing jar file or repo not found"

if i could open an interactive session and evaluate (core/configure-repositories!) i could see what repos are ending up configured

boot repl gives you that

oh cool

you could do boot -B repl to get a repl without the build.boot file being evaluated

if you suspect your build.boot is faulty

then you can do (load-file "build.boot") in the repl

so the repl task is dual purpose — for both project code and boot stuff

there is no separation

boot and project are the same

that’s really cool

boot just provides some functions and whatnot that you can require and use

but your build.boot is just a clojure program

you can do everything you can do on the command line in the repl

well except for starting another repl lol

i'm not sure what (boot (repl)) would do when you're already in the repl

so tasks are just fns with some extra metadata to enable cli invocation?

they're functions that are generated from the deftask macro, so they know how to accept command line arguments or repl arguments

but yes they're regular functions

there is also metadata, like you say, which helps boot find which tasks are available, for isntance

and also some things to help boot parse a command line with multiple tasks involved

also i just discoverd that you can do (boot (repl)) when you're already in a repl

it starts a nested one, apparently

^^ composability FTW

ok, thanks for the explainer

@spieden: the ins and outs of the command line stuff is here: https://github.com/boot-clj/boot/wiki/Task-Options-DSL

i’m still on lein but working with boot within cljsjs

much easier to debug what’s going on