Hello friends, I have to build a Lumo script @work (something that I never did) and I have a few questions for those who have answers : 1. Is there a “clojure” way to use promise/async/await (I am using puppeteer with headless chrome 2. Do you have some feedbacks on running nodejs generated with cljs script in Lambda ?

@baptiste-from-paris there is core.async for cljs, you can have go loops with a wait and some conditions

you mean wrapping wait/async calls into core.async ?

@baptiste-from-paris there's no cljs syntax for async/wait, I think there's a neat hack that was come up with in #lumo

(defn x [] (js/Promise. (fn [resolve reject] (resolve 42))))
(js* "(async () => ~{}(await ~{}))();" js/console.log (x))

ok, thx a lot @dominicm

How can I access process.env variables from a cljs app running on node.js?

(ns app.core
  (:require [cljs.nodejs :as nodejs]))

(nodejs/enable-util-print!)

(defn -main [& _]
  (println "your var: " (aget js/process.env "MYVAR") ))

(set! *main-cli-fn* -main)

node app/core.js MYVAR=foo

Your var:  nil

what about MYVAR=foo node app/core.js ?

Damn it 🙂

this is not ruby's rake, you have to use your bash-fu 🙂

and the process.env is a JSON object? Can I js/JSON.parse it and access all the keys?

@fbielejec no, it is just a JS object, AFAIK

@fbielejec If you want all the keys, (js-keys js/process.env)

thanks @mfikes , (.keys js/Object js/process.env) also works

(because its probably the exact same thing)

@fbielejec You can do (source js-keys) at a REPL to see how it works. FWIW, there is a ticket (CLJS-2340) that may result in js-keys simply delegating to goog.object/getKeys

This might be a beginner question, but I have a large json data file that want to have access to as a clojure map for a static site I’m developing (no backend, just cljs), can I just use :require?

I figure I’ll use either transit/read, edn/read or just JSON/parse, but curious how I can require the JSON in the first place

ajax the data

@conaw how will the data be deployed?

you can't require json, since json doesn't have namespaces for starters

@conaw You could slurp it at compile time with a macro, if you're not using bootstrapped cljs.