can someone help me to fix the syntax here: I’m confused of what should be used refer-macros or require-macros:

(:require  [cljs.core.async :refer-macros [go] :refer [<! !>]])

this seems worked:

(ns foo 
  (:require-macros [cljs.core.async.macros :refer [go]])
  (:require [cljs.core.async :as async :refer [put! chan <! >! close!]]))

@ag you can’t :refer-macros from cljs.core.async because they are in different namespace cljs.core.async.macros

Hi; has anyone tried using @darwin's dirac tools (repl) from boot/cljs-repl?

For some reason I have great difficulty passing in nrepl-opts

https://github.com/boot-clj/boot-cljs-devtools this may help, not sure though

@dominicm: great thanks!!

didn't see that

@anmonteiro: @darwin: Right, my problem from yesterday is not in the expression generated for ClojureScript but that I'm calling the same generation code from Clojure and from ClojureScript - but with a few differences and those differences mean what I get back when calling it from ClojureScript is backtick-quoted once or twice too often, so instead of a list I get back an unevaluated expression made of clojure.core/seq, clojure.core/concat, clojure.core/list etc.

I think I can fix this with a few reader conditionals in the generating code.

To treat the macro case and the call-in-CLJS case differently.

@jannis: unless you’re using bootstrap Clojurescript, reader conditionals won’t work

you’ll want to use something like this: https://groups.google.com/forum/#!topic/clojurescript/iBY5HaQda4A

JS question: If I have a chain of promises like (-> (js/fetch url #js {:method "POST"}) (.then #(.json %)) (.then #(handle %)) (.catch #(prn "Opps" %))) -- if handle raises an Error, this will be caught by the .catch handler. What if I don't want to catch those exceptions there?

I.e. I'd like an actual exception to be raised, not just an errback to be called

the promise handlers are async so you can't reraise the exception like synchronous exception

true

but my handle function may do nay kinds of operations that have nothing to do with this promise

so I don't want those exceptions if they occur to be caught by the fetch .catch method

hah, according to http://stackoverflow.com/a/30741722/239678 the way to throw inside a .catch block is to use setTimeout. The JS world really is weird and wonderful

@pesterhazy: you might not want to add such a dependency in your project for X reasons, but that’s the type of problems core.async solves really well

yeah, core.async wouldn't help in my case (it's about interop with a JS library)

@anmonteiro: I'm calling a function in a .cljc file from the macro and from ClojureScript, so there I can detect whether or not I'm "in the macro" or not. It's already working 🙂

core.async does not solves very well something that promise and rx streams (imho much better)...

it lacks of error handling and you should build your own, if you join that together to the idea of if every one uses core.async every library will use its own approach for handle errors...

it's not an option for me

core.async is very nice piece of software but it is not a silver bullet and I think it does not fits very well as promise abstraction

I just got a fighweel repl into the atom editor and its amazing

how?

gotta remove the CSP from atom's index.html

it's in app.asar.. unpack, edit, pack. good to go

https://clojurians.slack.com/archives/clojurescript/p1470201857002461

I understand that

but why this:

(:require [cljs.core.async.macros :refer-macros [go]])

whereas this

(:require-macros [cljs.core.async.macros :refer [go]])

works

I am confused and I don’t know how to explain to someone when should we use require-macros and when require with refer-macros.

@ag it is confusing 🙂 the rule is: refer gets cljs, refer-macros gets clj ... but it becomes cloudy when you introduce cljc 🙂

Initially I thought they both are basically the same - just the first form is deprecated. Apparently Clojurescript compiler thinks differently

they are different yes.

Macros can only be defined in Clojure (clj) and applied at compile time

(this is not strictly true because the bootstrap compiler exists now, but that's the easiest way to think about it)

There are other forms that work, such as putting clj macros and cljs code in a cljc and requiring with refer-macros

but I encourage you to avoid the syntactic sugar, because it is hard to keep track of in your head.

ie: always use require-macros imo

never use require refer-macros

(just my opinion)

more specifically to your question of why :require ... :refer-macros ... doesn't work... because that namespace cannot be required (there is no clojurescript file for that ns)

@ag http://blog.fikesfarm.com/posts/2016-03-01-clojurescript-macro-sugar.html

hi all, I was working on a proof-of-concept to implement a swagger-based API with a node/clojurescript backend. I keep running into an issue that perhaps one of you will understand

the issue, as far as I can tell, is that lots of the swagger libraries end up using other NPM libraries like uri-js

but this library has conditionals that act differently for compiled vs not compiled javascript, that I dont fully grasp

what I do understand is that when I run this in my cljsbuild, it is trying to compile those libraries and bad things happen

so, what I am wondering is: is this behavior of compiling node_modules configurable in the cljsbuild

?

or is this just a dead end

the end result is, that ends up getting skipped since cljs is trying to compile it

i was wondering if there is something like a cljsbuild flag, or perhaps an option in the nodejs/require form that allows it to be treated differently

@ghaskins im not sure what you mean by compiling these other libs. You can require node modules with js/require at runtime just as you would the built in libs

the meaning of compiled in a 3rd party lib is different than a cljsc concern

it seems like at line 6, its trying to compile http.js, etc

I'm trying to use :foreign-libs; the example showed the use of a url (http://...) to load the file, but my cljsbuild is giving a "no such file" error and simply appending the url to the classpath. What am I supposed to be doing?

but the problem is, all of those libraries basically shut themselves off if they are being compiled

for instance, snippet above wont define URI if COMPILED==true

try just npm installing them locally to your project and using node's require

and thus http.js ends up with a nil

i am unfamiliar with the details of packing up foreign libs, i know there was alot of work on that done recently, someone else will have to help

@pat: as far as I know, that is what i am doing….i have lein-npm reference the deps, they get pulled down into node_modules, and then I (nodejs/require) them in my cljs code

if you have done that i dont think you need to include that in your build config

sorry, missed a step, lein-npm def in project.clj, "lein npm install” pulls them into node_modules, and then (nodejs/require) at run time blows up

you mean do not reference them in lein-npm/project.clj and just npm-install manually?

under the :foreign-libs key in your build. if its npm installed, just js/require them

it seems the act of invoking the (nodejs/require) form is what triggers the Module._compile

ah, ok, let me google that

I am not familar with :foreign-libs but it sounds promising

nothing to google. just comment out that key

not sure what you mean: i dont have it currently

wait i think i may have mixed in shader's question

ah, ok, heh

that makes more sense

@ghaskins : clean your project, ignore 'lein npm'. just use npm manually to install package and then require globally through js/require

ok, ill try that

@ghaskins: if that works, then theres a problem with lein-npm or the package

well, I just downloaded it locally, and it's not giving errors when I give it the right path, so I assume that part is working

(not the package i mean)

how do I require it though?

just requiring the same name that I put in :provides doesn't seem to be working

@shader anything that is not cljs or goog needs to be accessed globally

you require the same thing you put in provides, but its a pseudo-namespace, have to use js/somelib to access it

for example: look at all the react wrappers out there. React is bundled in by you still have to use js/React.... to use it

sure, but the error I'm getting is "no such namespace"

where is that error

@pat: same error when I use pure npm plumbing instead of lein-npm

either when I run (require 'JSEncrypt) in the repl, or try to build a file with :require [JSEncrypt :as jse]

my guess its either an incompatiblity for this particular library with clojurescript, or I need to pass an option to the js/require

you can't alias it either. (ns foo.core (:require [some-js-lib])) (def a (.-a js/somelib))

so the alias caused the error?

we are talking about two different requires, ignore what i said to ghaskins

well, some reason it worked after I removed the alias...

I'm kinda confused

:require in you ns form is different that using js/require to use a npm package

but it seems to be working now

ok yeah its not a real ns, just a convenience

yeah, I rather assumed that

well, adding the alias back in didn't break it again, so something else must have changed

are you using figwheel

@ghaskins can you start just a simple node javascript repl and require it? theres no reason why cljs should be incompatible

sure, let me try that

@pat: same issue from repl

i was able to js/require most things, but the “swagger-tools” package blows up

perhaps its just not cljs compatible

actually all it takes is (js/require "uri-js")

@ghaskins i meant try a javascript repl

it seems most of the swagger libs rely on that, which perhaps is not cljs compat

understood, i am in figwheel

oh, you mean literally a js repl, not cljs?

@ghaskins : no a literal javascript repl. just start node: $node

ok

pardon me, I am not a node/js expert…what is the syntax to require from a pure node repl?

i tried that but it wasnt happy

@ghaskins https://nodejs.org/dist/latest-v4.x/docs/api/globals.html#globals_require

cool, thank you

yes, “require(‘uri-js’)” works in node repl, (js/require “uri-js”) blows up in figwheel with the same stack trade

trace

(as my run time problem)

I am reasonably confident its because of that Module.compile() being invoked, but I dont know enough about what the js/require form really does

hmm, it does seem there are options in the js/require form

https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/js.cljs#L224

maybe I need to tweak how its required

@pat yes, I'm using figwheel - seem to have broken again

@ghaskins thats bootstrapped cljs, not same require

oh

@shader hot-reloading code has its own state to consider. start clean without the alias, should be fine

@ghasking js/require is identical to using reuire from node. does it work without figwheel? ($ lein cljsbuild once)

^@ghaskins

I see the same behavior regardless of whether I do the js/require in figwheel repl or on cljsbuild output

though, I am using cljsbuild for the figwheel setup too

so that isnt surprising

@ghaskins to be clear, you tried a build without figwheel, just a $lein cljsbuild once, ran the file, same problem?

yes

@ghaskins bizarre

would a stripped down reproduction help?

im sure I could create a minimal test case of this

sure

so I have a clojure webserver that serves clojurescript, how can I pass environment variables into the clojurescript code?

same way you pass all other data 🙂

which would be?

ajax call into the webserver?

send EDN

depends on your app, but that's one good approach

yah that's kind of overkill

but would work

any other patterns.. I could serve the HTML file and inject javascript in script tags taht contains the ENV vars

kind of hacky

and really no different than the ajax call. browser still has to request a different resource

ok, i guess those are the options

thanks

@pat: https://github.com/ghaskins/cljs-urijs-problem

clone, “make && node js/demo.js"

blows up in the same way ive been seeing

Hey all. I have a protocol defined in one namespace and a record that implements that protocol stored in my app’s state. In a different namespace I pull that record out of the state. Now how do I execute a function on it?

I tried (.my-func rec) and get TypeError: rec.my-func is not a function

no interop needed ie (.function foo)

(require ‘[namespace.with.protocol :as p])
(p/my-func record)

or refer my-func from the protocol ns

@jr Thank you so much! I didn’t realize the function was defined in the ns versus in the protocol itself

@ghaskins i changed it to :optimizations :simple and it worked. so it looks as though whatever build system the lib author is using is interacting with our closure code somehow, node dependencies aren't resolving correctly

oh cool, you are awesome

thanks for taking the time to look

well simple is a pain. would have to dig deeper for a fix

yeah, probably best to say “swagger+cljs” isnt ready for prime time quite yet

when dnolen swings around ask him he may have idea whats going on

fwiw theres lots of ppl doing swagger on JVM

for server side anyay

yeah, probably is I am forced on node for other reasons

I mostly work on JVM clj but was forced to learn node/cljs because of an environmental factor

if you can find a way around that particular dependency you are probably fine

yeah, right now I have the cljs talking GRPCs fine…but problem is I cant currently surface HTTP2 through the load balancer

so, i was wondering if I could swap out the GRPC interface for swagger over HTTP/1.1 but I might have to tier it

maybe just use cljs as glue code, use it as a library

not sure what you mean

oh yes, i get you

thats exactly what I am thinking

cljs just for data processing, use all the node bs for endpoints

tag your functions with ^export tags and you'll be able to advanced compile too

[service-endpoint]-> [swagger::clj-jvm] -> [grpc::node -> sdk] -> backend

oh, i get you

problem is, I love clojure and loath javascript, heh

not sure I could cope

😉

yeah i hear that

but that grpc tiering kinda/sorta acts like a library

so that might work and allow me to stay mostly in clojure[script]

its a microservice architecture anyway, so splitting up the tiering is trivial

but thanks for all the help, it is greatly appreciated

are you trying to rig up API Gateway endpoints with a swagger spec?

well, what I wanted to do was surface the GRPC natively, but the version of HAProxy that is baked into OpenShift seems to puke on the binary HTTP2 payload

so, as an alternative, I was wondering if I could swap out the GRPC endpoint for something HTTP/1 based, like a basic swagger REST endpoint

ok i thought this was an AWS thing

no, openshift in this case

though perhaps similar problems

@ghaskins i put (set! js/COMPILED js/undefined) at the top and it worked

oh interesting

i def owe you a beer

ill play with that, that seems workable

thank you

@ghaskins no problem, goodluck

I was trying to use (.use app …) but my app was a standard (def app (js/require ..))

im thinking its something like (def foo (app.)) and then (.use foo) but its inclear to me

oh, maybe I just need to invoke it as a form

e.g. (.use (app))

yep, that worked, NM

(def app ((js/require “connect”))) is the same as ‘require(“connect”)()'