mach
mach copied to clipboard
juxt
A remake of make (in ClojureScript)
**minimal Machfile.edn to reproduce the error** ``` {mach/dependencies [[aero "1.1.2"]] hello (println "Hello")} ``` **error** ``` Writing Mach classpath to .mach/cp evalmachine.:98 throw ex; ^ Error: ENOENT: no such file...
``` ✘-127 ~/Documents/github.com/first-roll 12:02 $ sudo npm install -g @juxt/mach /usr/local/bin/mach -> /usr/local/lib/node_modules/@juxt/mach/bin/mach > [email protected] install /usr/local/lib/node_modules/@juxt/mach/node_modules/lumo-cljs > node scripts/npm_install.js || nodejs scripts/npm_install.js internal/streams/legacy.js:59 throw er; // Unhandled stream error...
With tools.deps now an option for defining the classpath, how should mach integrate with it? Looks like the `clj` and `clojure` scripts will now create a .cpache directory we could...
### Problem When specifying both produce and product where the product is a directory, mach fails with the following exception: ``` Error: EISDIR: illegal operation on a directory, open ''...
Need to ponder the idea of shipping Lumo with Mach, because the binary compiled download version of Mach is much faster to run (~400 ms).
Hello again, again :smile: (and sorry to bother so much) Today I tried to launch lumo straight from `mach` but failed. It looks like the main process shuts down as...
### Use case Set an `environment` variable using mach/constant ```clojure mach/constant {environment "staging"} ``` You are not able to use this constant in mach/props ```clojure mach/props [config (aero.core/read-config "conf.edn" {:profile...
Keys destructuring in mach/props doesn't create a globally accessible variable. ```clojure {mach/props [{:keys [datomic-user datomic-password aws-access-key aws-secret-key]} (aero.core/read-config "config.edn" {})]} ``` It is possible to use these local vars inside...
There is a basis protocol (Target) which exposes match? for whether or not a target matches. A sequential search is then performed over all targets for each input target. Example...
When I use the ref literal pointing at the result of a ClojureScript expression, it doesn't work as expected. For example, what should happen in the below case: ```` {...