@thheller i'd like to help with the documentation writing effort, how can i get started?

by which i mean, are there things in particular that you'd like documented but never have the time to document?

I want h2 too..

Is there docs for using shadow-cljs in clj now?

I got errors in my attempts

Exception in thread "main" clojure.lang.ExceptionInfo: missing instance {}
	at clojure.core$ex_info.invokeStatic(core.clj:4739)
	at clojure.core$ex_info.invoke(core.clj:4739)
	at shadow.cljs.devtools.server.runtime$get_instance_BANG_.invokeStatic(runtime.clj:11)
	at shadow.cljs.devtools.server.runtime$get_instance_BANG_.invoke(runtime.clj:8)
	at shadow.cljs.devtools.api$get_or_start_worker.invokeStatic(api.clj:104)
	at shadow.cljs.devtools.api$get_or_start_worker.invoke(api.clj:99)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:125)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:111)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:115)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:111)
	at build.watch$_main.invokeStatic(watch.clj:12)
	at build.watch$_main.invoke(watch.clj:8)
	at clojure.lang.AFn.applyToHelper(AFn.java:152)
	at clojure.lang.AFn.applyTo(AFn.java:144)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.core$apply.invokeStatic(core.clj:657)
	at clojure.main$main_opt.invokeStatic(main.clj:317)
	at clojure.main$main_opt.invoke(main.clj:313)
	at clojure.main$main.invokeStatic(main.clj:424)
	at clojure.main$main.doInvoke(main.clj:387)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.main.main(main.java:37)

@seako cool! I want to document all the things. I never know what to document since I wrote the thing and know how everything works. Anything helps really.

@jiyinyiyong in clj call (api/with-runtime (api/watch ...)) if you want a short lived runtime. (shadow.cljs.devtools.server/start!) if you want to start and leave it running in the background.

2 | (ns app.updater (:require [respo.cursor :refer [mutate]]))
   3 |
   4 | (defn updater [store op op-data]
   5 |   (case op
---------^----------------------------------------------------------------------
 Cannot infer target type in expression (. G__35616 -fqn)
--------------------------------------------------------------------------------
   6 |     :states (update store :states (mutate op-data))
   7 |     :content (assoc store :content op-data)
   8 |     store))

didn't see this warning before, what does it mean?

=>> clj -m build.compile
Exception in thread "main" java.lang.AssertionError: Assert failed: (map? http)
	at shadow.cljs.devtools.server.worker$start.invokeStatic(worker.clj:106)
	at shadow.cljs.devtools.server.worker$start.invoke(worker.clj:106)
	at shadow.cljs.devtools.server.supervisor$start_worker.invokeStatic(supervisor.clj:30)
	at shadow.cljs.devtools.server.supervisor$start_worker.invoke(supervisor.clj:23)
	at shadow.cljs.devtools.api$get_or_start_worker.invokeStatic(api.clj:108)
	at shadow.cljs.devtools.api$get_or_start_worker.invoke(api.clj:99)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:125)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:111)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:115)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:111)
	at build.compile$_main$body_fn__29460__auto____31659.invoke(compile.clj:9)
	at build.compile$_main.invokeStatic(compile.clj:8)
	at build.compile$_main.invoke(compile.clj:7)
	at clojure.lang.AFn.applyToHelper(AFn.java:152)
	at clojure.lang.AFn.applyTo(AFn.java:144)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.core$apply.invokeStatic(core.clj:657)
	at clojure.main$main_opt.invokeStatic(main.clj:317)
	at clojure.main$main_opt.invoke(main.clj:313)
	at clojure.main$main.invokeStatic(main.clj:424)
	at clojure.main$main.doInvoke(main.clj:387)
	at clojure.lang.RestFn.applyTo(RestFn.java:137)
	at clojure.lang.Var.applyTo(Var.java:702)
	at clojure.main.main(main.java:37)

(ns build.compile
  (:require [shadow.cljs.devtools.api :as api]
            [shadow.cljs.devtools.server :as server]
            [clojure.java.shell :refer [sh]]))

(defn -main []
  (api/with-runtime
    (api/watch :browser)))

turned out I need full examples running shadow-cljs in clj

works fine when I use (server/start!)

ah, hmm for watch you can’t use with-runtime. only for compile.

yeah, start! should work

oh... right, I forgot to change the function

working now with api/with-runtime (api/compile ...)

I really would not recommend running shadow-cljs via clj. it is just strictly worse than using shadow-cljs directly

just because you can doesn’t mean that you should 😉

don’t forget calling (server/stop!)

well... I'm trying to solve the problem of compiling with shadow-cljs twice

hmm?

as described https://github.com/thheller/shadow-cljs/issues/147

clj won’t solve that for you

I will put the scripts in a .clj file, not touching it from REPL actually

clj will always launch a new JVM so I’m not sure what you are hoping to gain

during my assets building, I need to start shadow-cljs twice from npm script

no you do not

create ONE clojure function

(ns build.compile) (defn do-something [] ...)

then I need to run clj to run that.

shadow-cljs clj-run build.compile/do-something

in that function do whatever you want

my build tool was npm scripts.. it does not run Clojure

eg. call (api/watch ...)

anyway I have to write Clojure code..

yeah you’ll need to write clojure … but why use clj?

are you suggesting that I run clj code with shadow-cljs instead of clj

yes, why not?

didn't try clj-run sub-command before

it does literally the same stuff clj does

well it actually does more ..

they look same too me. guess I don't need to duplicate deps in deps.edn if I call shadow-cljs clj-run

how about the warning? Cannot infer target type in expression (. G__35616 -fqn)

not seen it before, only got it when I call APIs

dunno, does it happen with clj-run?

haven't tried yet

clj has a few issues with dependencies, it sometimes loads old versions

it resolves differently than lein or boot. don’t know why … it is alpha so be careful.

tried with clj-run, no warning now

thanks

I will try migrate some of my build scripts to Clojure.. hope it runs well

just pushed [email protected] which should start a bit faster. if you already have ssl configured it now supports http2 as well.

@thheller You mentioned in the cljs channel that shadow-cljs has support for using dependencies from npm. Is there a minimal example somewhere of how to require those dependencies in clojurescript code? Should it work the way clojurescript's :npm-deps is supposed to?

@tomc https://code.thheller.com/blog/shadow-cljs/2017/11/10/js-dependencies-in-practice.html

:npm-deps is supported when libs use it. in your project you directly npm install (or yarn) yourself

minimal example you can clone https://github.com/shadow-cljs/quickstart-browser and use that as a quickstart

shadow-cljs - config: /Users/chen/repo/mvc-works/coworkflow/shadow-cljs.edn version: 2.0.122
shadow-cljs - starting ...
Exception in thread "main" java.lang.AssertionError: Assert failed: (map? http)
	at shadow.cljs.devtools.server.worker$start.invokeStatic(worker.clj:106)
	at shadow.cljs.devtools.server.worker$start.invoke(worker.clj:106)
	at shadow.cljs.devtools.server.supervisor$start_worker.invokeStatic(supervisor.clj:30)
	at shadow.cljs.devtools.server.supervisor$start_worker.invoke(supervisor.clj:23)
	at shadow.cljs.devtools.api$get_or_start_worker.invokeStatic(api.clj:95)
	at shadow.cljs.devtools.api$get_or_start_worker.invoke(api.clj:86)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:112)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:98)
	at shadow.cljs.devtools.api$watch.invokeStatic(api.clj:102)
	at shadow.cljs.devtools.api$watch.invoke(api.clj:98)
	at build.watch$_main.invokeStatic(watch.clj:9)
	at build.watch$_main.invoke(watch.clj:7)

what does this error mean?

what are you doing?

(ns build.watch
  (:require [shadow.cljs.devtools.api :as api]
            [shadow.cljs.devtools.server :as server]
            [clojure.java.shell :refer [sh]]))

(defn -main []
  (server/start!)
  (api/watch :browser))

if you use clj-run you don’t need server/start!

well...

how about api/watch

@thheller thanks a lot

I think it caused the error. the error remains without server/start!

I need more information, I can’t tell what you are doing

which command do you run?

trying to launch a watch server from API

which command do you run?

yarn shadow-cljs clj-run build.watch/-main

is a server running?

no server

turned out not a good idea to start watch server from a script.

you can do that no problem

what's the right code to start a watch server in Clojure code?

(api/watch :browser)

hang on. I think I found the issue.

so the issue is that clj-run only does a with-runtime which is a lightweight runtime that doesn’t start the embedded server

but watch needs the embedded server

I did not expect anything to run watch via clj-run

a worker?

I think I’ll change it so it just launches the full runtime instead

the issue with watch is that it starts a background thread

that background thread does not keep the process itself running

so it starts, compiles once and then just exits

not what you want

what are you trying to do exactly that shadow-cljs watch the-build doesn’t do?

just exploring, never tried it before

if that feels better, maybe I would rely on npm scripts less

I can make it work easily but it does require you managing threads which is not very fun

"del": "rm -rf dist/*",
    "release": "shadow-cljs release browser",
    "compile-ssr": "shadow-cljs compile ssr",
    "html": "node target/ssr.js && cp entry/manifest.json dist/",
    "build": "yarn del && yarn release && yarn compile-ssr && yarn html"

these or which npm scripts are we talking about?

never mind, actually I would use shadow-cljs command line, if launching it from Clojure is not better.

I’m trying to help you here but I first need to understand what you are doing

there are several things I can do … just need to figure out which makes the most sense

these lines does not include watching part, they are for releasing.

(ns build.release
  (:require [shadow.cljs.devtools.api :as api]
            [shadow.cljs.devtools.server :as server]
            [clojure.java.shell :refer [sh]]))

(defn -main []
  (println (sh "rm" "-rf" "dist/*"))
  (api/with-runtime (api/release :browser))
  (api/with-runtime (api/compile :ssr))
  (println (sh "node" "target/ssr.js"))
  (println (sh "cp" "entry/manifest.json" "dist/")))

I added this script, and it does run faster than my previous version

please stop doing a new ns for everything

(ns app.build) (defn release [] ...) (defn watch [] ...)

will merge them into one file later...

you can invoke functions directly with clj-run, makes things much easier to organize imho

ok so the build.release works with clj-run right?

it's a feature from shadow-cljs, I didn't see clj calls a specific function from CLI

clj can’t call functions directly, only -main yeah

yes, it works, runs faster.

if you use clj-run you also don’t need api/with-runtime

(defn release []
  (println (sh "rm" "-rf" "dist/*"))
  (api/release :browser)
  (api/compile :ssr)
  (println (sh "node" "target/ssr.js"))
  (println (sh "cp" "entry/manifest.json" "dist/")))

cool

so api/watch starts a background thread. its basically an async function. it returns as soon as the first compile completes

(defn watch []
  (api/watch :browser)
  (api/repl :browser))

this would work since the api/repl would “block” until you exit the repl

but thats annoying since you can’t switch anything

no, there's an error

Exception in thread "main" java.lang.AssertionError: Assert failed: (map? http)
	at shadow.cljs.devtools.server.worker$start.invokeStatic(worker.clj:106)
	at shadow.cljs.devtools.server.worker$start.invoke(worker.clj:106)
	at shadow.cljs.devtools.server.supervisor$start_worker.invokeStatic(supervisor.clj:30)

yeah you can’t do that NOW. I can make it work though

oh...

the question I want to answer is how to manage the threads most effectively

I think I need to sleep now, too late in here

thanks again

what do you want watch to do that shadow-cljs watch does not do?

if you are literally just calling api/watch that doesn’t make much sense

I was just trying to see if the watch server would launch

I’ll change the embedded server logic so the Assert failed: (map? http) goes away

or, maybe trying to find out if clj CLI can replace npm scripts

still want to figure you what you are trying to do exactly to see if I can make things easier

npm scripts is kinda annoying since it starts a new process for each command

which CLJ just isn’t built for

well, if it is, I have to accept

don’t give up so easily … this is not rocket science

I just need to understand what you are trying to do

I’m still just guessing here

my daily work is in typescript and react, not much time to spend on here recently

I'm just trying to get familiar with them and figure out if things can be easier

found no direction yet

too late,, really going to sleep

sleep well, good night.

bye

is there an equivalent to lein deps :tree with shadow

i can’t remember..

shadow-cljs pom ; mvn dependency:tree

does the JVM stuff

not yet. I want to add it eventually. didn’t even know about the mvn stuff but that seems to work

yeah, that could be added to shadow’s docs. someone else just told me about it.

is there a place where people like myself can add to docs?

the wiki