Clojurians Log v2

I've got a web app to analyze and test and break. It's in plain js. Does boot have tools to help me embed a cljs repl so I can start experimenting with symbols i find my coworkers have written?

My goals are to call their js functions with generated test data, and maybe provide some functions to help them write tests.

@mathpunk i'm not aware of anything in particular, but there is a cljs browser extension for chrome that you might find helpful

@alandipert Cool. I'm sufficiently unfamiliar with the running environment of a web app that ill take all the help i can

@miikka @crisptrutski can we get a boot-cljs-test release that includes the Doo 0.1.10 fix?

Is there a 'standard' place to set BOOT_JVM_OPTIONS so that all users get it for a particular project?

It looks like I either need to set the env var myself or create a wrapping boot to do this

@danielcompton FWIW, we took the latter approach at World Singles. We have a build/bin/boot which is our wrapper and we have the actual boot file as build/bin/boot-core (so we can control the version of the main Boot app, as well as ensuring the same, expected shell script is available throughout the project, across all tiers).

Our wrapper parses our version.properties file to get the "pinned" version of Clojure to use with Boot as well.

I don't suppose putting JVM options in boot.properties would work would it?

How would you ensure every developer/every machine had the correct boot.properties data?

check it in at the root of your project?

I have one there, I assume it's doing something, but maybe not 🙂

Does Boot read boot.properties from the current directory when it is run? (I don't know -- it would seem sensible tho')

Yup, testing indicates it does.

So, that would work for any static options you wanted.

We computer BOOT_JVM_OPTIONS dynamically in our wrapper script, depending on various parameters and host environment etc.

Hmm, JVM opts doesn't seem to be picked up?

BOOT_JVM_OPTIONS="--add-mod abab" works fine, when it should throw

i don't think boot_jvm_options are picked up from boot.properties

😢

I only tested BOOT_CLOJURE_VERSION, sorry.

it would be cool if it did tho. i don't know if there's a technical reason why not