hey, guys. I use clojurescript to call some javascript library function, but this will make this in the called function invalid. Is it relative to the compiler? @thheller

how do you call it?

(.thatFn the-object 1 2 3) will keep the-object as this?

.bind and other tricks don't work so well with CLJS currently

No, the bare javascript function must call by ((.-thatFn obj) arg1 arg2)

why not (.thatFn obj arg1 arg2)? whats the point of getting the fn off the object first?

It's npm library for javascript.

you are not calling (obj.thatFn)(arg1, arg2) in JS either?

(.-fn obj arg1 arg2) I also try it, but doesn't work too.

remove the -

.-fn is short for getting that property`. (.fn ...) is short for calling that fn

(.-fn obj) will get the function, so the first way doesn't matter, I have verified it.

yes exactly. (.-fn obj) will GET the function. (.fn obj) will CALL the function

I know, thank you. You are right!

Hi everyone. I'm trying to learn clojurescript to create an AWS lambda, but I'm having trouble getting a REPL working in emacs/spacemacs. I create REPL via cider-jack-in-clojurescript and see [nREPL] Starting server via npx shadow-cljs -d nrepl:0.6.0 -d cider/piggieback:0.4.1 -d refactor-nrepl:2.5.0-SNAPSHOT -d cider/cider-nrepl:0.22.0-beta11 server. After Select ClojureScript REPL type: node, I see [nREPL] Direct connection to localhost:37269 established, but I get an error Unhandled java.lang.AssertionError Assert failed: (keyword? repl-env). I'm using version 2.8.51, node 10.16.3, and spacemacs [email protected]

My shadow-cljs-edn:

{:source-paths ["src"]
 :dependencies []
 :builds {:app {:target :node-library
                :exports {:handler test.main/handler}
                :output-dir "target"
                :output-to "target/main.js"}}}

You need to add the dependencies to cider as well

And you also need piggieback

https://docs.cider.mx/cider/basics/clojurescript.html

This is how I got it working

I have cider-nrepl and piggieback installed. The repl seems to work if I choose custom and do (shadow/watch :app) (shadow/node-repl :app)

Is there a way to print out the deps.cljs :npm-deps dependency tree ?

Hi, I'm having trouble with a react-native project, expo is trying to connect to the wrong websocket because it is getting the wrong lan ip. How can I override the ip being used?

Using https://github.com/thheller/reagent-expo

@superstructor no. there is no tree. its a flat map but you can use npm list or so after they are installed

My issue is probably related to https://github.com/thheller/shadow-cljs/issues/482

https://shadow-cljs.github.io/docs/UsersGuide.html#repl-trouble-react-native has the solution

we have a module that represents one namespace, we're pulling a function from a npm package - it works fine on the dev environment but once we build the app we have this error Uncaught ReferenceError: $jscomp is not defined when calling toAscii

do you not use :advanced? that name shouldn't exist anymore?

which build target is this? $jscomp is used by the closure compiler for polyfills.

Hi! Updating shadow-cljs from 2.8.39 to 2.8.45 (or .51) is unfortunately breaking our REPL setup on the final NPM build of our project. We checked for the usual culprits but nothing did the trick except reverting to 2.8.39. This is an :npm-module that's being consumed by a Webpack project. From JS we have

window.CLOSURE_BASE_PATH = '/javascripts' // Should match our assets location
  require('cljs/shadow.cljs.devtools.client.browser')

cljs.user> 3
3
cljs.user> (first [1 2])
ReferenceError: cljs is not defined
    at eval (eval at shadow$cljs$devtools$client$browser$global_eval (webpack-internal:///./build/cljs/shadow.cljs.devtools.client.browser.js), <anonymous>:1:1)
    at eval (<anonymous>)
    at Object.shadow$cljs$devtools$client$browser$global_eval [as global_eval] (webpack-internal:///./build/cljs/shadow.cljs.devtools.client.browser.js:878:16)
    at eval (webpack-internal:///./build/cljs/shadow.cljs.devtools.client.browser.js:887:44)
[...]

hmm that is probably caused by the introduction of the global-eval fn. https://github.com/thheller/shadow-cljs/commit/1470c6d2d06195d01ba2b486ef6f730c36b51840

hmm not sure what to do about the. I introduced the global-eval to fix another issue

you could try copying the current browser.cljs https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/devtools/client/browser.cljs and just replacing the #(global-eval .. with (js/eval ...

seems weird this doesn't work though. I thought I ensured the npm-modules properly exports to global

too tired to think about that now. if you open an issue I'll take a look over the weekend

Will give that a try, thanks!