I have an inconsistently occurring bug to report -- In Emacs, if I start M-x cider-jack-in-cljs it usually (90% of time) fails with below output. One in 10 runs inexplicably succeeds.

[:app] Configuring build.
[:app] Compiling ...
[:app] Build completed. (608 files, 1 compiled, 0 warnings, 3.68s)
To quit, type: :cljs/quit
user> [:selected :app]
shutting down ...
cljs.user> 
*** Closed on Mon Aug 19 18:38:22 2019 ***

[:app] Build completed. (608 files, 607 compiled, 0 warnings, 16.99s)
To quit, type: :cljs/quit
user> [:selected :app]
cljs.user> 

output from the nrepl-server buffer:

shadow-cljs - server pid exists but server appears to be dead, proceeding without server.
shadow-cljs - config: /Users/quest/repos/ns/browser/shadow-cljs.edn  cli version: 2.8.46  node: v12.8.0
shadow-cljs - running: lein update-in :dependencies conj [nrepl "0.6.0"] -- update-in :dependencies conj [cider/piggieback "0.4.0"] -- update-in :dependencies conj [refactor-nrepl "2.4.0"] -- update-in :dependencies conj [cider/cider-nrepl "0.21.1"] -- run -m shadow.cljs.devtools.cli --npm -d nrepl:0.6.0 -d cider/piggieback:0.4.0 -d refactor-nrepl:2.4.0 -d cider/cider-nrepl:0.21.1 server
shutting down..

* Whether I launch the browser or not (when prompted) seems to have no effect. * Deleting .shadow-cljs/builds/app/dev/ana/cljs seems to raise success rate to 100%. I notice that it's a 5MB+ folder, which probably causes the compilation step to take longer. * However deleting .shadow-cljs/builds/app/dev/ana/re_frame still results in a noticeable amount of failure -- but it's only a 500K library, so maybe similar to deleting my ana/northstar/browser (project's) folder

My guess is some sort of race condition that's negated by sufficiently increased compilation time. Unfortunately the guess is all I have, but I'll assist with troubleshooting however possible

Running on OSX Mojave 10.14.6, GNU Emacs 26.2

@quest try limiting the amount of RAM shadow-cljs uses by setting :jvm-opts ["-Xmx2G"] (or 1G) in project.clj

dunno why deleting cache files changes your success rate since compilation recreates the exact same state again anways

no clue what emacs does when running processes. maybe it is somehow monitoring the processes or causes it to have other resource constraints

but other people have reported issues with cider as well and limiting the memory seems to help

hi everybody! is there a place in shadow-cljs.edn to add es6 js files I want to add locally (not coming from npm). My use case is that I'm using a library that needs me to provide it objects that extends from others and I think I prefer to leave those as es6 js code instead of replicating that in clojurescript with goog.object/extend etc

https://shadow-cljs.github.io/docs/UsersGuide.html#classpath-js

just put it next to your .cljs files

thanks a lot!

can react and react-dom be benefit from optimizations of closure compiler?

the react-dom bundle size is pretty large

in theory they can but it is not recommended and requires tweaking by hand

could also break with any new release and most OTHER libraries don't work

also doesn't make it that much smaller

so not worth the effort

I want to reduce the bundle, in my case now it's about 370kb but use on not so good network

is that gzip'd?

Yes, gzip'd

hmm yeah thats a bit large. did you create a build report? https://shadow-cljs.github.io/docs/UsersGuide.html#_build_report

Yes

There're few dependencies I have plan to remove, like expound

clojurescript seems too large? maybe you included cljs.pprint?

I don't know why, is it normal?

click the little expand icon in front of clojurescript

It's about 5731 lines of cljs

cljs/core.cljs 232.04 KB cljs/pprint.cljs 98.44 KB cljs/analyzer.cljc 95.13 KB cljs/spec/alpha.cljs 54.73 KB cljs/spec/gen/alpha.cljs 23.27 KB cljs/spec/test/alpha.cljs 12.15 KB cljs/stacktrace.cljc 5.56 KB cljs/reader.cljs 3.46 KB

Ohh, pprint

hmm do you use self hosted stuff?

no

hmm then cljs.analyzer shouldn't be in there either

wait, what you mean by self hosted

Is that if I use it in macro, that cljs will be included as well?

depends on how you included it?

Just like pprint, I didn't use it, just forgot to delete the require in ns form

if you use the web UI (default at http://localhost:9630)

there is a little UI thingy to tell you why a namespace was included in a build

wait a moment, I'm going to start this

pprint unfortunately isn't compatible with DCE in the way it is currently written https://clojure.atlassian.net/browse/CLJS-2885

web UI looks great

if you select your build and hit compile

it'll have a "Build Namespaces" select box at the bottom

select cljs.analyzer and it'll tell you why it is included (which namespace included it)

but I guess you already found it 😉

reitit.coercion.spec -> spec-tools.core -> spec-tools.impl -> cljs.analyzer.api -> cljs.analyzer

....sad

interesting. someone should open a bug report there 😉

the spec-tools is using this...

yeah but it very likely doesn't actually need it

cljs.analyzer.api is very likely only used from the CLJ macro side

so including it in the CLJS side is pointless

cljs.spec is also not so small

yep https://clojure.atlassian.net/browse/CLJS-1701

I found one thing, report is not support if there's multiple modules?

sure it is

https://code.thheller.com/demos/build-report/huge.html example report has multiple

but In my project it doesn't, I have two moudles, one is :base :base {:entries []}

:strip-type-prefixes #{"cljs.spec"} where can I put this

I also just want to remove all spec

doesn't work for spec anymore

an empty :base module doesn't make sense when you only have 2 modules

In my dev build, I have another module called devcards, main and devcards both depends on base

dev build? you are likely using shadow-cljs wrong if you have a build named :dev

thats not how it works at all 😛

no, actually it is app.

devcards should likely be its own build

definitely wrong to include that as a :module

should I make it a build?

a good rule to remember for :modules is that you should only use them if and only if ONE user may end up using ALL modules

ie :devcards likely won't be used by your users and only by you during development

therefore it should be in a different build

But If I make it another build, I know I can start two build in shadow, but Can I connect to two browser environment in one cljs repl?

shadow-cljs watch app devcards starts two builds

no to the REPL. they are separate

but they would be anyways?

you likely aren't loading your app and devcards in the same browser tab?

You know, cider (basically except cursive) rely on repl to provide auto-completion and many other features.

Cursive doesn't rely on that no

Yes, I know

but it's easy to solve, I can just start two emacs instances

you can also just load your main entries in the devcards build

I'll make it another build.

so they have the code loaded

but yeah cider relying on nrepl so much may be a problem with too many builds

yes, it is

I just remove pprint

how can I easily remove all specs? I have a few cljc file

unfortunately can't

alright

need to do something like this https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/core.cljc#L24

good

or move all specs in a separate files and include them via :preloads

How can I add conditional dependencies depend on :dev and :release with tools-deps

:preloads

:preloads?

currently I have devtools, but it appears in the report.

in the build report?

yes

https://shadow-cljs.github.io/docs/UsersGuide.html#_preloads

No, I mean

In the WEB UI

if you included that properly via preloads then it shouldn't be in there

the web ui shows you what you built

but pprint is still in report

so if you pressed the compile button it shows you a :dev build

and in web UI I found it is required by devtools

press the release button instead to see the release deps/namespaces

I'm trying to regenerate a report

org.clojure/clojurescript is still 400k

well whats in it?

with spec that seems about right

Yes, only one thing, cljs.analyzer. I have to switch a router to remove that.

OH, I can patch that maybe

https://github.com/metosin/spec-tools/blob/master/src/spec_tools/impl.cljc#L17

https://github.com/metosin/spec-tools/blob/master/src/spec_tools/impl.cljc#L5

can probably switch that to :clj instead

I hate .cljc so much. so misunderstood and often used incorrectly

sometimes i like it because can share code, especially configuration.

yeah but it is so easy to get wrong, especially with macros

I guess they are doing this to support the self-hosted stuff but even then it seems wrong

but yeah conditional code include is tough and needs a better solution

don't know the reason, maybe caused by eval loader

sometimes, the chrome hangs

depends on how much code you load I guess. from your build-report it doesn't seem too excessive. but dunno how much dev stuff you add (eg. re-frame-10x adds a whole lot)

often happened when I switch build

not happened in common usage

dunno. never happens for me so you'll have to debug a bit yourself

I copy that file change that macro to always return nil. I think it won't affect anything in my project

cljs is 296 kb now

I was trying to use module split in my project, and it works pretty good. however it won't load module in a browser, (that is our mainly target browser), no tools or any information to debug. So have to give it up.

The result is good to me now, it's gizp'd 300kb. I'm going to remove a few more things. thanks for the great help today!!

shadow is awesome!

shadow-cljs is a great tool & the level of support thheller provides here is exceptional. If you agree, please consider subbing https://www.patreon.com/thheller/overview to keep it rolling 🙂

;; shadow-cljs configuration
{:source-paths
 ["src/dev"
  "src/spill"
  "src/test"]

 :dependencies
 [[org.clojure/core.async "0.4.500"]
  [reagent "0.8.1"]
  [re-frame "0.10.6"]
  [bouncer "1.0.1"]
  [com.andrewmcveigh/cljs-time "0.5.2"]
  [clj-commons/secretary "1.2.4"]
  [venantius/accountant "0.2.4"]
  [binaryage/oops "0.7.0"]
  [binaryage/devtools "0.9.10"]
  [day8.re-frame/re-frame-10x "0.3.7-react16"]
  [day8.re-frame/tracing "0.5.1"]]

 :builds {:app {:output-dir "web/root/js/shadow"
                :asset-path "js/shadow"
                :target :browser
                :closure-defines {"re_frame.trace.trace_enabled_QMARK_" true}
                :preloads [devtools.preload day8.re-frame-10x.preload]
                :modules {:app {:init-fn spill.app.core/init}}
                :main "spill.app.core"
                :devtools {:http-root "web/root"
                           :http-port 8080}
                :compiler-options {:optimizations :none}}}}

with this configuration i can't run re-frame-10x

what i am doing wrong

:main "spill.app.core" that does nothing and can be removed

:compiler-options {:optimizations :none} also does nothing and can be removed

besides that I think it may require an extra closure-define?

oh and :preloads belongs in :devtools

or into :modules {:app {:init-fn ... :preloads [...]}}

@thheller @stefan.age thank you very much it's working now 🙂

Is it possible to configure something like an :asset-path to go along with [:devtools :watch-dir] ? Watch-dir does not work for me, and I think it is because the URLs are not generated like :watch-dir expects (just /some/path under :watch-dir) - in my case I have a prefix.