Hello all, what is the use of async and await of javascript?

in clojurescript?

the closest analogs in my opinion are go blocks (`async`) and <! (`await`) from core.async

@fabrao Dunno about await but async has something to do with doing tests on asynchronous things.

@levitanong I think he’s asking about javascript’s async/await keywords, which are closest to go blocks

Oops, silly me!

Is pr-string data structures a good way to serialize edn or is there something more space efficient?

For any Cursive + cljs users out there. The REPL that I end up with by running a lein figwheeel task is pretty lame, up/down arrows do not search history so I end up copying and pasting all the time. Should it be better?

I start a regular clj repl from cursive and call "cljs-repl" from the figwheel api

works flawlessly

I'm trying to use existing npm packages inside my cljs project. I can make the example from https://anmonteiro.com/2017/03/requiring-node-js-modules-from-clojurescript-namespaces/ with left-pad work. However, when I try another package (`apollo-client`), it doesn't work:

I did add the npm package to :npm-deps (just the way I added left-pad).

I seem to be able to load the apollo-client, but I can't do anything with it:

(require '[apollo-client])
nil
cljs.user> apollo-client
#object[ReferenceError ReferenceError: [...]$node_modules$apollo_client$index is not defined]
nil
cljs.user> apollo-client.
#object[ReferenceError ReferenceError: apollo_client_SLASH_ is not defined]
nil
cljs.user> apollo-client/ApolloClient
#object[ReferenceError ReferenceError: [...]$node_modules$apollo_client$index is not defined]
nil

checking the apollo-client module source: it has this structure:

-- packages
   |
   |- ...
   -- apollo-client

And packages/apollo-client/rollup.config.js:

import build from '../../rollup.config';

export default build('apollo.core');

^^ how can I make the apollo-client run in cljs?

@kurt-o-sys I think if you just want to be productive A) just build your JS separately and use a single include B) try an alternative tool like shadow-cljs

:npm-deps is for the long haul, there’s still a lot of work to do, and not just us (Closure Compiler)

oh, ok... so it's better to avoid :npm-deps for now?

or for the adventurous with some time to spare to help push it forward 🙂

if your goal is to just get something done - yes avoid it

:npm-deps works OK for some simple things and stuff like just React

yeah, that's my goal 🙂 . OK, let me see how shadow-cljs works. thx.

hi, im trying to use lein-asset-minifier to minize the compiled reagent app's app.js file and I get this error: JSC_READ_ERROR. Cannot read: /home/user/sample/target/cljsbuild/public/app.js at (unknown source) line (unknown line) : (unknown column)

can you use this as an argument in cljs? does it get munged away from this in the emitted code?

yes you can, I use that name when I pass this explicitly

but in that situation a collision would be undetectable? if it was the this argument or the keyword this in javascript?

"this" is nothing in cljs

you need to use this-as for accessing it

or use (js* "this")

ah ok. so there are steps to prevent the collisison

thanks

(defn stuff [this]
  (+ 3 this))

;; becomes 
letfn_bug.core.stuff =
(function letfn_bug$core$stuff(this$){return ((3) + this$);});

yep

thanks for the help

👍!