@bhauman Figured out a way to have separate REPLs for CLJ and CLJS.. not perfect but good enough for now:

1) Start Clojure REPL, e.g.: clojure -m figwheel.main --build dev repl

2) Launch a separate terminal and use leiningen to connect to existing REPL, e.g.: lein repl :connect nrepl:127.0.0.1:1234 (replacing 1234)

3) Start figwheel-main from second REPL, e.g.: (figwheel.main/start "dev")

@bhauman If you feel it's useful enough to include in the figwheel-main lib I can create a pull request

I'm not getting what you are doing here

why do you need to have figwheel running twice?

that seems bad

Oops sorry.. the first step should be: (clojure -m rebel-readline.main)

oh that makes more sense

and you start a nrepl server in the this clojure main process?

Oh yes in my first instance.. (missing lots of steps!) 🙂

The only caveat(s) is having to leiningen for CLJS and no rebel-readline in CLJS

are you using this from vim?

or only in the terminal?

These are separate terminals but connected to it with one Vim instance (fireplace)

So three terminals altogether: Vim, Clojure REPL, ClojureScript REPL + Figwheel

oh I gotcha

fireplace talks to the terminal repls?

or is fireplace connecting to the nREPL server?

fireplace is talking through nREPL and Piggieback

and fireplace doesn't provide a REPL inside the editor?

Not really.. there's a very, very limited one-line evaluator.. they call it the Quasi-REPL.. it sucks

For Common Lisp Vim has slimv. It has an excellent REPL built-in. But the Clojure interop isn't great so I use fireplace

OK this setup is cool, because I think it will work with vscode and with VIM

now that I understand how it works, I think I can come up with an interesting solution

too bad rebel-readline doesn't work over nREPL yet

but that will come in the future

Right - yup I like having the REPLs separate

actually I can't think of a better way to do this right now, you kinda have to choose with repl you want to work with rebel-readline

I guess there's no way to somehow combine lein repl :connect ... and lein trampoline run -m rebel-readline.main?

nope

but you could make it so that the cljs repl gets rebel-readline instead of the clojure repl

I think?

Yup good point I can

Probably a better idea for now as I'll be using ClojureScript much more heavily

yeah If you want to write this up that would be great

Yup no prob

probably with rebel-readline in the cljs repl

ok

which doc file should it sit in?

put it in the docs/docs directory as a separate file

and just ensure that it is last

If you are familiar with github pages development, you can use it jekyll serve from the docs directory

ok cool will try that

I'm having an issue with npm-deps where goog is saying undefined name to path for a dependency of the module I'm trying to use. I've tested my project.cljs with react and left pad and it works fine. any advice on where to go from here?

also here is my project.cljs and source if you want to check it out https://gist.github.com/mjrb/1903851fe692656329d5d9eb33205b01

@www.w.com123 Potential workaround: https://gist.github.com/mfikes/abd3389e5cefb06ff15124c243cd0060

has anyone experienced in web dev cljs and bidi been successful using a prefix in their url routes, such as a #?

Hello all, I need to define a javascript function in clojurescript env. I tried to use ^:export but it includes the namespace before. Is that possible to define without namespace?

@fabrao you can do (ns your.ns) (defn some-fn [] ...) (js/goog.exportSymbol "theFunction" some-fn)

that would create a global theFunction() in JS

@thheller Thanks, I´ll try it

@mfikes thanks for that, but I'd need to use the sdk package to login and get a client to get a mongo connection

Right now my work around is to use yarn and foreign libs to access the stuff. Id probably have to write externs regardless if I used foriegn libs or npm-deps right?

someone correct me if i’m wrong, but, in theory, libraries that get included via :npm-deps get run through the closure compiler. if they survive that process, they’ll get minified along with the cljs code and you shouldn’t need externs. it isn’t clear how much js code can really survive closure compilation, however, so you may need to futz with externs after all. for :foreign-libs included libraries, I’d turn on automatic inference if I were you. I think it works pretty well now. If you are using a lot of npm stuff, I’d further recommend you use shadow-cljs as your build tool instead. including npm packages and inferring externs works very smoothly with it.

Thanks I'll look into shadow

npm deps work fine with ClojureScript

there’s no reason to use another tool other matter of taste/preference

@www.w.com123 https://clojurescript.org/guides/webpack

ClojureScript has externs inference so you don’t have to write externs

you just have to write a bit of boilerplate glue that shadow-cljs elides - but this hardly matters in long term projects IMHO

You should avoid :npm-deps unless you want to live on the cutting edge - or want to help advance that feature

@dnolen I followed that guide and that's how I currently got the project working, but when I tried to turn on adnvanced compilation (with infer externs) it said window.Ld was not defined or something which sounds like something weird happened with the externs

For context and if anyone is interested I'm working on a cljs library for mongodb stitch (a serverless platform that gives you secure client side db access)

(and also server side function and integrations with other services)

@www.w.com123 that doesn’t sound like an externs problem

it sounds like you passed index.js into your build somehow

did you get the guide working by itself without modification?

I’ve tried it with fairly non-trivial stuff - React Datepicker etc. and I haven’t run into any issues myself

Google login (https://developers.google.com/identity/sign-in/web/sign-in) instructs to redefine the global onSignIn function to get the information after they've signed in. From browser console, this works from me; but how can I redefine this global function from my cljs file?

@worlds-endless just use goog.object/set on js/window:

(goog.object/set js/window "thing" "foo")
=> nil
(goog.object/get js/window "thing")
=> "foo"

Thanks, @lee.justin.m. Turns out it was even easier: (set! js/onSignIn on-google-signin)

(which is probably the same thing under the hood)

people often suggest using goog.object/set, though I’m not sure what if any difference there is to just using set!

That's an interesting question; if goog.object/set is better than set!, I wonder why it isn't just rewritten as an alias?

for example, in the docstring of aset, it suggests using goog.object/set instead of just using set!. i’m not quite sure why

there's some weird malarkey that happens when closure starts optimizing

AFAIK the rule of thumb is: 1. Object made & set through interop syntax, can use interop syntax 2. Object made by other JS? Use goog.object

I'm trying to update a set of CLJSJS packages. I run boot on the build.boot and it seems to 'complete', including buiding deps.clj, writing the pom stuff and writing the jar. But I can't find the poms or jar. Anyone know where this stuff is written or what otherwise may be wrong?? Thanks!