Any obvious gotchas for the {:figwheel {:on-jsload "some.thing/here" }} config not working? I get the little clojurescript icon flash, so it looks like the new code is being pushed down the wire, but it's not re-rendering the view. I can call the function from a cljs repl and it works with no issue.

make sure it's a function and not the result of calling the function

I understand there are some changes to running cljs, but I'm not sure what they are. Is this qs reflective of the changes? https://clojurescript.org/guides/quick-start

Does it still depend on Java? Someone said you don't need to run Java directly but I didn't understand what that meant

@drewverlee ClojureScript requires Java unless you’re using bootstrapped - i.e. Planck or Lumo (independently installable)

Planck is self-contained I think now? (\cc @mfikes), Lumo needs Node.js (I guess it’s self contained too)

They are both self-contained. Installable via brew and other means.

(Lumo bundles its own Node.js binary, essentially.)

@drewverlee these options are popular for scripting as they start fast- but most app dev is happening via ClojureScript that runs against JVM

@drewverlee You are probably referring to the changes in this draft of Quick Start, where you can see that you no longer type java to run things (unless on Windows, but that will ultimately change too): https://github.com/clojure/clojurescript-site/blob/quick-start-1.10/content/guides/quick-start.adoc

I’m trying the new 1.10 cljs quickstart and tried to compile this file: https://github.com/lambdaisland/birch/blob/master/src/birch/core.cljs with target node:

clj -m cljs.main --target node --output-to main.js -c hello-world.core

This is my deps.edn:

{:deps
 {org.clojure/clojurescript {:git/url “”
                             :sha “2f233d633f6dc44823105fd544685fc4da43ac6c”
                             }
  org.clojure/tools.cli {:mvn/version “0.3.5”}}
 }

(I removed the code that uses the coloring lib)

clj -m cljs.main -re node -m hello-world.core is probably what you want

if you want to compile something that just runs you need kick it off yourself in the source

yeah:

clj -m cljs.main -re node -m hello-world.core "."
WARNING: Use of undeclared Var hello-world.core/-main in file <cljs repl>
...

@borkdude cljs.core/*main-cli-fn* is also a thing, if you set that then when you compile -c w/ -t node then whatever you set that dyn var to will be invoked

yes, that’s what I needed! thanks

np

How do I get everything inside with main.js file without any references to the out folder?

Add a -O simple

I tried clj -m cljs.main --target node --output-to main.js -c hello-world.core -O simple but that didn’t work for me

Move the -O to the left...

It is an init opt IIRC

that’s better…

@borkdude If you end up seeing improvements to the draft instructions here, I could incorporate them. One change I'll make is to simply output to main.js without a path. https://github.com/mfikes/clojurescript-site/blob/issue-177/content/news/2018-03-12-clojurescript-command-line.adoc#creating-a-node-app

Here is the associated PR as well https://github.com/clojure/clojurescript-site/pull/178

looks fine to me. Why post it as a news article, or will it also be included in guides/references?

With Reagent I’m always looking through several news posts to find the latest API additions and how they work 😉

Because the news post has a heavy emphasis on all the stuff you can do with cljs.main (whereas Quick Start is trying to just get you going without illustrating all the neat stuff that cljs.main can do)

There is some repetition, though, granted

Here are all the planned doc drafts. Feedback on the PRs welcome: https://gist.github.com/mfikes/bdbe214f03abac88ae384adb1ac26490

News article is great. But it’s also great to not have to dig through news articles to get the full picture is what I meant with my reference to Reagent

Found a small typo dirctly on hte, not sure if that’s relevant

Right, there is a reference page as well. (News is ephemeral) https://github.com/mfikes/clojurescript-site/blob/issue-172/content/reference/repl-and-main.adoc#compiling-source

is it possible to use rebel-readline with cljs right now?

seems like cljs.main needs to take -m option instead of rebel readline. is there another way to invoke?

Just trying 1.10.145 with :nodejs in CIDER and it seems I get a "banner" ever time I eval???

cljs.user> :abc
ClojureScript 1.10.145
:abc
cljs.user> (+ 1 2 3)
ClojureScript 1.10.145
6
cljs.user> 

@tmarble Fixed in master https://dev.clojure.org/jira/browse/CLJS-2640

@mfikes excellent! (I'm only 3 days late to the party :)

cljs.user=> (hello-world.core/-main “foo” “bar”)
foobar
nil
cljs.user=> (require ’[hello-world.core :refer [-main]])
clojure.lang.ExceptionInfo: Invalid :refer, var hello-world.core/-main does not exist

@dpsutton no easy integration of rebel-readline and cljs.main yet

it can be done for certain

as cljs.main is easy to compose over

you can do it yourself by making a main that wraps cljs.main with a rebel-readline, its a great exercise

@bhauman @dpsutton If you do this, it will bridge cljs.main to rebel-readline with the browser REPL being the "inner" one:

clj -Sdeps '{:deps {github-mfikes/cljs-main-rebel-readline {:git/url "" :sha "262b801da65ec5260e295ed9a478084fa67e58cd"}}}' -i @/bridge.clj -m cljs.main -re rebel-readline-cljs

I'm working on how to pass in the inner REPL via a -ro option, so if you want node it will give you an wrapped Node REPL, for example.

it would be cleaner for me to just wrap it

Yeah, in the end you should 🙂

@mfikes but honestly that’s also not bad, -i / -m are :main-opts

so you can put that behind a alias and use it anywhere

but overriding the repl-env is the hard part

I suspect it could be -re rebel-readline-cljs with -ro {:wrapped-re "node"}, but I haven't put much thought into it.

this of course looks differently to me because I designed rebel readline so that you can easily wrap it around anything

@bhauman so rebel readline needs access to repl-env, it can’t just start the REPL?

that seems odd if true

It isn't really a REPL, right? It enhances a wrapped REPL env

rebel-readline has inline eval

yeah it's not a repl

at all

it provides example repls

and in the cljs case its just a toy

the readline is separate from the repl entirely

and this is why it needs a connection

yeah I dunno, if you need to wrap repl-env then it won’t work in other interesting cases - i.e. Clojure/ClojureScript socket REPLs running under one VM via component or whatever

so I would say in general wrapping repl-env is not a good idea

it will work in all of these cases

how it gets its data is abstracted

the repl-env is only one way of getting it

ah k, good

yeah you really want it to compose, otherwise you’ll write your own version of everything

@dpsutton This will run cljs.main with Node, if you are interested in that variant

clj -Sdeps '{:deps {github-mfikes/cljs-main-rebel-readline {:git/url "" :sha "74ef9e83e5edd0421b468b581e4b03e8c74c497f"}}}' -i @/bridge.clj -m cljs.main -re rebel-readline-cljs

why does this happen? https://clojurians.slack.com/archives/C03S1L9DN/p1520800504000010

@mfikes @dpsutton clojure -e "(require 'cljs.repl)(require 'rebel-readline.cljs.repl)(let [cljs-repl cljs.repl/repl*] (alter-var-root #'cljs.repl/repl* (fn [x] (fn [env opts] (with-redefs [cljs.repl/repl* cljs-repl] (rebel-readline.cljs.repl/repl* env opts)))))nil)" -m cljs.main

it's evil

with a simple modification it could be a simpler redef

thanks @bhauman I'm porting some stuff from cljx to cljc and wanting to see what it looks like to only use clj tools.

@borkdude make something minimal so someone can repro

I couldn’t repro some of your earlier things

@dnolen ah, my bad, I had (ns hello_world.core)